Join Raymond Camden for an in-depth discussion in this video What you should know, part of Learning Ionic 2.
- [Instructor] Based on my experience with mobile development and Ionic, there are four things I consider crucial for success. First and foremost, you should have a basic understanding of Apache Cordova. You do not need to be an expert, but you should definitely have it installed, be aware of how the CLI works, and have at least a passing familiarity with Cordova or PhoneGap development. To be clear, you do not have to be an expert, but if you know nothing at all, I strongly recommend looking at the docs, and going through a few basic examples just to get an understanding of how it works.
The absolute best resource for learning web standards or just double-checking you're doing something right, is the Mozilla Developer Network. Mozilla are the folks behind Firefox, but their dev network is not Firefox-specific. Now we come to the heart of this prereq, Angular 2. Ionic is based on Angular. At a very high level, you can think of Angular 2 as a way of organizing a web application so it's easier to build.
It separates your view where all the UI lives, from the code that handles interactions. So on submitting a form, you know, do something. And the code that handles working with remote servers, for getting and sending data for example. It does a heck of a lot more, and it's worthwhile to dig deep into it, but you will not need to become an expert in order to use this with Ionic. However, I highly recommend going through both the QuickStart and guide tutorials, if you have no familiarity with Angular 2.
Also, know that if you have Angular 1 experience, well, it's best if you forget it. Angular 2 is vastly different, and it's best if you don't think of it while learning Angular 2. Finally, be aware that no matter how good you are, things are going to break. Knowing how to debug your Ionic application, will be crucial to your learning. DevTools, primarily the Chrome version, will be the best tool you have to help you in debugging your applications.
You can also use Chrome and Safari's DevTools for debugging on the actual hardware.
- Making a default application
- Exploring application files
- Adding navigation and UI components
- Using a hard-coded detail view
- Adding the SW provider via CLI
- Making a list and a details page
- Adding a loading widget
- Using native and market Ionic resources