Overview
Many companies maintain a separate repo for web and native mobile applications, and sometimes yet another for mobile web. Historically you may hear that ‘wrapped applications’ are slower and choppy. This is no longer the case – if your application is structured correctly.
By using Ember.js with Cordova, it is possible to have a single code base powering all four (desktop web, mobile web, native iOS and native Android). Outside of the immediate cost/programming time savings, this technique enables you to build future iterations faster and stop the out of sync issues plaguing many code bases (e.g. the Android app has different features to iOS).
Objective
Learn how to write a single code base which works on all platforms without the presumed drawbacks.
Target Audience
Developers/managers working on one of the three mentioned platforms, and who wish to no longer maintain separate code bases for each platform.
Assumed Audience Knowledge
A general knowledge of how either backend, front-end or mobile applications are developed is helpful.
Five things audience members will learn
- How to build a single code base working on all platforms
- What changes (if any) are required in the code base to achieve this
- How to avoid common draw-backs of wrapped applications, such as perceived slowness
- How to access native phone functions without muddling up the code base
- How such applications are packaged and deployed
