150 likes | 230 Views
Multi-Platform Application Development Strategies for Disconnected Mobile Applications. Gunnison Consulting Group, Inc March 29, 2012. Gunnison at Census. Providing full lifecycle software engineering at Census since 1994. TMO in Context. The Near Term Goal. Technical Approach Options.
E N D
Multi-Platform Application Development Strategies for Disconnected Mobile Applications Gunnison Consulting Group, Inc March 29, 2012
Gunnison at Census Providing full lifecycle software engineering at Census since 1994.
Why this is hard… • The technical challenges: • Battery Life • Memory Management (esp. on iOS) • .NET on ARM (Windows 8) • Thread Management (esp. in Android) • Consumer focus • Strong differences in platform-specific languages • Laptop vs. Tablet • Gartner recommendations: • “Over analysis is a risk in an immature market.” • Rule of Three: “If an organization is targeting three or more device platforms, if they have three or more applications, or if they have three or more back-end systems, then the multichannel or cross-platform tools typically yield better project results during the course of three to five years than native tools.” • “Enterprises need to consider whether they can mitigate platform uncertainty by adopting a single platform strategy for 2011 to 2012.” (Choosing Cross-Platform Tools for Native Mobile Applications, G00211990) (Magic Quadrant for Mobile Enterprise Application Platforms, G00211688) (Critical Capabilities for Mobile Enterprise Application Platforms, G00212257)
HTML5 and the Cloud Image Source: http://smallbiztechnology.com/
What about connectivity? • Web Storage • Application Cache • Web SQL • Indexed DB
Native Code: How much design can be shared across platforms?