Downloaded 241 times
Uploaded byDipesh Mukerji
Latest Trends in Mobile App Development
The document discusses various options for multi-channel mobile app development including native, mobile web, and platform approaches. It outlines the challenges and advantages of each approach such as native providing full device capabilities but being costly to develop and maintain. Mobile backend as a service (MBaaS) is presented as a solution allowing developers to leverage enterprise-grade backend functionality without having to build it themselves.
More Related Content
Similar to Latest Trends in Mobile App Development
![Support, Monitoring, Continuous Improvement & Scaling Agentic Automation [3/3]](https://cdn.slidesharecdn.com/ss_thumbnails/agenticcommunityseries-day3-cfd-251120170304-ddef8112-thumbnail.jpg?width=640&height=640&fit=bounds)
Latest Trends in Mobile App Development
- 1. Multi-channel App Development LatestTrends in Mobile App Development Dipesh Mukerji, Kony Inc.
- 2.
- 3.
- 4.
- 5. Native Approach Challenges • Mustknow device specific development language skill set • Can’t port over to other devices • Costly • Have to go through app store or direct distribution • Potential for large device footprint • High maintenance Advantages • Leverage full device capabilities • Full offline device storage • Best performance • Richest UI • Must go through app store or direct distribution • Gaming capabilities • Plethora of app developers • No limits
- 6.
- 7.
- 8. Mobile Web Approach Challenges •Less stable than native • Pulls in data much more slowly than native • Browser fragmentation • No app store discoverability • May take longer to generate revenue • Scarcity of mobile web developers • Less offline capabilities • Poor gaming capabilities • Not as UI rich as native • Less device access capabilities Advantages • Leverage effective web search technology for discoverability • Native mobile developers are getting more expensive • More capable than HTML4 • Multimedia support • Cost efficient • Cross-platform • Less maintenance • Multivariate testing • Faster time-to-market • Smaller device footprint • Can be wrapped in hybrid format
- 9.
- 10.
- 11. Platform Approach Challenges • Unsupportedfeatures • Restricted use of personal tools • Possibility of slow performance • Vendor lock / restrictions • May not be as UI rich • Not every feature is cross-channel Advantages • Ease of use • Re-usability of code • Easy availability of plugins • Fastest to market • Lower total cost of ownership • Support for cloud services • Single code base across all devices • Security / Authentication • May support other elements of SDLC • Build native, mobile web, hybrid and mixed mode apps • Future proofing
- 13. • Operating systemdeveloped by Samsung, Intel and Linux Foundation • Covers usage in Mobile Devices, Camera, SmartTv, In-vehicle Entertainment • Too much dependent on Android • BadaOS & Meego failure to compete with Google and Apple • Huge profit contributed by Samsung Well – know product to Google • Opportunities in IVI industry • Samsung’s own products are some of the largest selling products in the world What? Why?
- 14. Tizen Architecture (forMobile) Applications Web Applications Web Framework W3C/HTML5 Device APIs Web Runtime Core Application Framework Graphics & Input Multimedia Web Messaging Location Security System Base Connectivity Telphony PIM Kernel Linux Kernel & device drivers
- 15. Benefits and challenges •Samsung brand already well known and also one of the biggest electronic manufacturers • Joint cooperation with Intel and Linux • Blue Ocean market for SmartTv, Camera, IVI • Samsung can apply Tizen to all its products • Support from NTT Docomo and Jaguar • Similar concept with Android • Late comers in Mobile OS Industry • Samsung products already closely related with Android, Threat of loosing trusts • Previous failure in Bada and Meego Project • Late entering the market for Mobile OS Strength Weakness Opportunity Threat
- 16.
- 17. The Developer View Extensivetime spent on back-end development Enterprise-grade back- end services No scalability Elastic scaling Silo development Open Standards Vendor lock-in Freedom & Flexibility
- 18. Mobile Backend-As-A-Service (MBaaS) Enterprise-GradeCloud Services Create rich app experiences without having to worry about back- end functionality Identity Integration Orchestration Messaging Sync Storage
- 19.
- 20. What To Consider •How large is your user base and how tech savvy are they? • What do your users want? • What devices are your users on? • What are your operational and maintenance cost requirements? • What UX and/or UI experience do your users require? • Are you looking to be in the app store? • Is vendor lock a concern?
- 21. App Development Architecture ProvisioningAccount Management Authentication & Authorization Reporting & Analytics Monitoring Billing KonyCloud Foundation Back-EndAs AService Messaging SyncIdentity Integration StorageOrchestration 3rd Party and Native SDK’s Kony Studio Native Web Hybrid Multi-channel Framework & Tools Manage Deploy Test Define Design Build Full End-To-End Lifecycle DevelopmentTools&Frameworks
Editor's Notes
- #3 Native SDK’s:AppleAndroidWindows PhonesBlackberryWeb:HTML5TizenOpen Standards:DojoJQuerySenchaPhoneGapPlatforms:KonySAPIBMAppceleratorDeveloper Platforms:TelerikXamarinMBaaS:KinveyFeedHenryAnyPresenceParseStackmobKidozen