How to use this template?

How can you use the elements of this template.

Once you purchase the starter, you have all the code to your disposal. You can modify the app anyway you want, but here are two major ways it can be done.

1. Use the Full App as a base to create your app

This means that the template is itself an Ionic app, so you don't need to create another app. You can use the template app as a base for your app and just delete the pages you don't want, and add what is missing.

If you plan to use many of the pages and features offered by the template, then I suggest you to go with this option.

For example, if you are looking to create a Tinder like app, use the Tinder cards page, the profile page, login page, chat page etc for the major structure. Delete other pages which are not required

2. Import Full App pages into an existing Ionic 5 app

If you only want to use some specific pages or components and you already have an existing Ionic 5 app. e.g. You want to import the Tinder Cards page into your other app

Copy the page folder

Locate the Tinder Cards folder in the code.

Now, copy the contents of the folder, both home and tindericons folder to your existing app.

In some cases, the pages are using a service for data etc. E.g. In case of Tinder, we use data from data.service You will have to import this service into your new app as well

Import dependent services along with pages

All pages have their styling included within the folder, so you don't need to copy any styles from Global.


Add the new route to your routing file such assrc/app/app-routing.module.ts

Shared Components

In some cases, the pages use Shared components. For example, the Multiple Slider page contains 4 different components, imported from src/app/components If you are using any such page in your app, make sure you also import the required components imported in the page

Imported components look like an HTML tag, something like this



All assets are kept in src/assets You can copy the assets related to your page from this folder, or use your own.

Keep in mind to keep assets folder as direct child of src because the production build expects it so. If you change the location, the production build might not be able to find the correct assets path