From version 1.1.0, the template includes 2 files:
It's the same app but the first one is configured to be used with Cordova and the second one with Capacitor. You can choose which one to use.
Let's go through the files and folders of the app.
Our Capacitor project will have
ios and an
android folder at the root of the project. These are entirely separate native projects that should be considered part of your Ionic app, this means you need to check them into source control and edit them in their own IDEs. I suggest you to read more about Capacitor in this post https://ionicthemes.com/tutorials/about/native-cross-platform-web-apps-with-ionic-capacitor
In the root of the project we have the following important files and folders:
The npm packages installed in the project with the
npm install command.
when building the app for different platforms (like iOS or android), this folder will be automatically generated with all the files needed. (only for cordova project)
when building the app for different platforms (like iOS or android), this folder will be automatically generated with the required cordova plugins like keyboard or splashscreen. (only for cordova project)
when building the app for different platforms (like iOS or android), this folder will be automatically generated with the app resources like the logo and the splash screen image. You should put your own resources here.
This is the most important folder and where the majority of the app will be developed. Here we have all the files that make our ionic app and is the location where we will spend most of our time.
This folder is generated automatically and you shouldn't change anything from here. It's where all the compiled files will go.
Main configuration file for the Angular CLI.
As every modern web application, we need a package system and package manager to handle all the third-party libraries and modules our app uses. Inside this file you will find all the dependencies and some other handy stuff like the npm scripts that will help us a lot to orchestrate the development (bundling/compiling) workflow.
Main configuration file, it needs to be in the root path as it’s where the typescript compiler will look for it.
We have already talked about the configuration for the workflow enough, now let's dive in the details of the
Inside of the
/src directory we find our raw, uncompiled code. This is where most of the work for your Ionic app will take place.
When we start the scripts that handle the bundling/compilation workflow, our code inside of
Under this folder you will find the following important folders and files:
Has all the components, modules, pages, services and styles you will use to build your app.
In this folder you will find sample images, sample-data json’s, and any other asset you may require in your app.
Under this folder are configuration files used by the Angular CLI to manage the different environment variables.
For example we could have a local database for our development environment and a product database for production environment.
When we run
ng serve it will use by default the dev environment.
It includes all the theming, variables and sass mixins to be used in our ionic app.
This is the main entry point for the app, though its purpose is to set up scripts, CSS includes, or start running our app. We won’t spend much of our time in this file.
This file extends
tsconfig.json main file and adds some specific configuration for the app. It’s then used in
This file extends
tsconfig.json main file and adds some specific configuration for the server. It’s then used in
This file is the app manifest to be used for the progressive web app. We will explain more about this in PWA section.
The App folder is the largest folder because it contains all the code of our ionic app. It has all the components, modules, pages, services and styles you will use to build your app.
This is the core of the project. Let’s have a look at the structure of this folder so you get an idea where to find things and where to add your own modules to adapt this project to your particular needs.
We designed this ionic project with a modular approach.
We strive to showcase an advanced app module architecture so you get a better idea on how to structure and scale your project. Again, modules are great to achieve scalability.
/app folder there are also some important files:
This serves as the skeleton of the app. Typically has a
<ion-router-outlet> to render the routes and their content. It can also be wrapped with content that you want to be in every page (for example a footer). In this app we added the side menu in this file.
It’s the Angular component that provides functionality to the html file I just mentioned about. In this template we have all the code for the side menu.
This is the main module of the ionic project.
Here we define the main routes. Child routes of other lazy modules are defined inside those modules. These routes are registered to the Angular
RouterModule in the
In this folder you will find images, sample-data json’s, and any other asset you may require in your app.
Here you will find all the variables, mixins, shared styles, etc, that will make your app customizable and extendable.
Here is where you will change the main colors of the app to match your styles.
Maybe you don’t know Sass? Briefly, it is a superset of css that will ease and speed your development cycles incredibly.