Product Code: IT021-000005
The huge level of interest in mobile application development has driven a noisy debate over whether developers should be writing native applications, web-based applications (using HTML5), or hybrid applications that borrow from both approaches.
- The real answer to the debate over HTML5, hybrid, and native is that each approach makes sense under different circumstances. It is not simply a question of choosing one option over the others. Indeed, it is likely that your organization will adopt each of the approaches in different situations.
- The architecture and design of the server-side are important elements of your application, as, ideally, the server-side functionality you implement in support of your application should be reusable across multiple application types.
- Understand the key differences between the different approaches.
- Learn about the importance of architecture in successful mobile application development.
- What factors should influence my decision to develop mobile applications using HTML, native, or hybrid approaches?
- What steps should I take to ensure that my mobile applications are robust, secure, and adaptable in the face of change?
Table of Contents
- Ovum view
- Key messages
- It is not a question of "which approach," but rather "which approach,
- All three approaches will have a place within your organization
- Set the technology dogma aside and establish a mechanism that helps you
select the right approach for each different application
- The technologies that underpin the different approaches are evolving
- Innovation is driving change
- HTML5 is focused on improving the mobile experience,
- There is no agreed final HTML5 standard at this time
- Can frameworks save the day?
- Case Study: The Financial Times
- HTML5 tools and frameworks
- jQuery Mobile
- Intel App Framework 2.0
- Sencha Touch
- There is a cost associated with adopting a framework, even if the
framework itself is free
- Hybrid development
- Native development
- The Apple ecosystem
- The Android ecosystem
- The Blackberry ecosystem
- The Windows ecosystem
- A fourth category is emerging: native cross-platform development
- A number of factors will influence your choice of approach for any
- Your choice will be governed by the type of application you're developing
- If data security is a major concern, develop native applications
- If high-quality video is essential, native applications will have a
- For most enterprise apps, HTML is likely to be more than adequate
- The emphasis you place on Architecture and design will make or break
- Without adopting an architectural approach, your developers will be less
productive and your application will cost more
- An architectural approach can speed up development, simplify security
and audit, and save money
- Key features of the mobile application broker layer
- You do not necessarily need to buy middleware to implement a layered
- Recommendations for enterprises
- Consider architecture and security from the very first app
- Your first foray into internally developed mobile applications should
- Watch the evolution of mobile application broker technology
- For internal applications, HTML5 is nearly always going to be the best
- Don't forget data security
- Recommendations for vendors
- The mobile application broker represents a significant opportunity
- Don't limit your ambitions to supporting phones and tablets
- Price your tools and middleware pragmatically
- There will be three viable application ecosystems, and you should pay
attention to them all
- Further reading
- Ovum Consulting
- Figure 1: Relative merits of the different approaches
- Figure 2: Mobile app development "hell"
- Figure 3: An architectural approach to mobile application development