Native vs Hybrid
Why still native sdk
- Common UI Views for better user experience
- Navigation and history stack
- It offers full access to the mobile platform
and not web sdk
- Doesn’t offer full access to the mobile platform
- Doesn’t provide rich, native-style UI components and interactions
- You’ll probably spend way too much time bringing native look and feel
HTML5 framework for hybrid mobile apps.
Build on angular, sass.
Uses cordova/phonegap for creating running building deploying mobile apps.
Native like performance and beautifully designed
Because they strongly believe HTML5 would rule on mobile over time, exactly as it has on the desktop.
- Native Focused
- Performance Obsessed
○Hardware accelerated animations
○Minimal DOM Manipulation
○Remove 300ms tap delay
- Plain old CSS
○80+ reusable mixins
- Boilerplate app structure ready for customization
- Preconfigured tools: Gulp, Sass, Bower, etc.
Prerequisites Before starting
- AngularJS ( UI router, custom directives, $scope and controllers )
- Sass ( optional )
Getting started / Install
$ npm install -g cordova ionic
Getting started / Create
$ ionic start myApp [ blank | tabs | sidemenu ]
Getting started / See
$ ionic serve [ –lab ]
Common cli commands from cordova
$ ionic platform add [ android | ios ]
$ ionic platform emulate [android | ios ]
$ ionic platform build [android | ios ]