Book Image

Learning Ionic, Second Edition - Second Edition

By : Ravulavaru
Book Image

Learning Ionic, Second Edition - Second Edition

By: Ravulavaru

Overview of this book

Ionic makes it incredibly easy to build beautiful and interactive mobile apps using HTML5, SCSS, and Angular. Ionic also makes app development easier, faster, and more fun. This hands-on guide will help you understand the Ionic framework and how you can leverage it to create amazing real-time applications. We begin by covering the essential features of Angular 2, and then dive straight into how Ionic fits in today’s world of hybrid app development and give you a better understanding of the mobile hybrid architecture along the way. Further on, you will learn how to work with Ionic decorators, services, and components, which will allow you to build complex apps using the Ionic framework. We will take a look at theming Ionic apps using the built-in SCSS setup. After that, we will explore Ionic Native, and you will learn how to integrate device-specific features, such as notifications, with the Ionic app. To complete our learning, we will be building a Rider app, using Ionic and Uber API, to book a ride. Next, you will learn how to unit test, end-to-end test, monkey test, and execute device testing on AWS Device farm. Then, we will take a look at migrating the existing Ionic 1 apps to Ionic 2 and deploy them to the App Store. The final chapter on Ionic 3 wraps up this book by explaining the new features of Ionic 3 at the time of writing this book. By the end of this book, you will be able to develop, deploy, and manage hybrid mobile applications built with Cordova, Ionic, and Angular. All the examples in this book are valid for both Ionic 2 and Ionic 3.
Table of Contents (13 chapters)

Angular 4

Since the launch of Angular 2, the Angular team has been working towards making Angular a stable and reliable framework for building applications. On 23 March, 2017, the Angular team released Angular 4.

What? Angular 4? What happened to Angular 3!!

Simply put, the Angular team adopted Semantic Versioning (http://semver.org/) to manage all the packages and dependences within the framework. In this process, one of the packages (@angular/router) has moved a complete major version ahead of the other packages, something like the following, due to the changes to the router package.:

Frameworks

Versions

@angular/core

v2.3.0

@angular/compiler

v2.3.0

@angular/compiler-cli

v2.3.0

@angular/http

v2.3.0

@angular/router

V3.3.0

Due to this misalignment and to avoid future confusion, the Angular team went ahead with Angular 4 instead of Angular 3.

Also, the tentative release schedule...