Mobile Application Development Strategy
- 2. Key parameters Business needs Enterprise IT roadmap Infrastructure Cost/Time Security & reach Skills Dev Operations Devices User experience Performance
- 3. Mobile Web VS Mobile App Mobile web •Responsive web page adjusting to different screen sizes •Existing web development/support skills •Existing infrastructure •Broad reach Mobile App •Leverage native device access •Pure offline access •Pure native user experience •High performance (LOB)
- 4. • What is Xamarin? Xamarin is a platform that enables Microsoft’s C# and .net developers to build iOS and android native apps using native interfaces and APIs but leveraging the shared C# code between iOS, Android and Windows platforms • What is Cordova? (Hybrid app) Cordova is an open source API set in javascript which enables the access of native device functions (such as camera, calendar, etc). Apps using cordova are packed using platform specific SDK and can be made available directly from the device’s apps store • What is Windows universal apps? Universal apps leverages shared code written using Visual Studio and at the same time supports unique experiences across all windows devices including windows phones. The app packages can be deployed via windows store on any windows device Source: Wiki.com & msdn.com
- 5. Phone’s data and hardware access Performance User experience Development/Maintenance time and cost Security Offline support Responsive web Cordova Xamarin Native app Low High Key indicators
- 6. Mobile app development: Choose a platform App needs to operate on multi devices Needs unique device capabilities Xamarin Budget constraints Cordova .Net or Web developers Xamarin Cordova Windows 8 devices only Build Universal windows apps .Net developers Xamarin Build native NoYes Yes No NoYes Yes No Web?.Net? Yes No
- 7. Iterative design thinking & app development Design Prototype Test and Learn Improve Major release Repeat..
- 8. Summary • Choose according to the needs of the enterprise and cost/time/quality – one size does not fit all • For CYOD/BYOD, start from responsive or adaptive web applications to cover broad spectrum of devices and resolutions • For use cases where we need native iOS apps, start with Xamarin but prepare for iOS development skills • For windows based company owned devices, use universal windows apps
Editor's Notes
- #3: Offline support good in HTML 5 based mobile web but best in native apps Access to phones hardware and native functions Maintenance and support lowest in web but highest in native Build cost investment highest in native least in web TARGET – company owned device – Go native - broad reach BYOD – Go web or Apache cordova (web development with SDK but needs to use app store)
- #4: Web pages in responsive design can leverage the SAP Fiori design principles and these apps can be deployed using apache cordova as native apps if needed Offline support good in HTML 5 based mobile web but best in native apps Access to phones hardware and native functions Maintenance and support lowest in web but highest in native Build cost investment highest in native least in web TARGET – company owned device – Go native - broad reach BYOD – Go web or Apache cordova (web development with SDK but needs to use app store)
- #5: Definitions taken from respective official web sites
- #8: Can use standard market tools such as Build, Specflow, etc by SAP to prototype and design