Cover Image
市場調查報告書

行動APP的開發:HTML5 VS Hybrid VS Native

Mobile Application Development: HTML5 vs. Hybrid vs. Native

出版商 Ovum, Ltd. 商品編碼 300156
出版日期 內容資訊 英文 15 Pages
商品交期: 最快1-2個工作天內
價格
Back to Top
行動APP的開發:HTML5 VS Hybrid VS Native Mobile Application Development: HTML5 vs. Hybrid vs. Native
出版日期: 2014年03月28日 內容資訊: 英文 15 Pages
簡介

大眾對行動應用程式開發的關注,掀起了所謂開發業者到底該寫原生應用程式或使用HTML5基於網路的應用程式、還是同時雙方皆用的Hybrid(混合)應用程式這個爭議。要HTML5?還是Hybrid,或是用Native(原生)這個爭議的解答,在不同的狀況下皆有不同的立論,所以不是該選何者這麼單純的問題。

本報告提供行動應用程式開發上程式語言的調查分析,概述各個程式方法特徵,解說成功開發APP上的重要架構,同時彙整決定行動APP開發所使用的語言之影響要素,為您概述為以下內容。

摘要

  • 發展要素
  • Ovum的見解
  • 主要的訊息
  • 不是「選擇哪個方法」的問題,不如說是「什麼時候該用哪個方法」的問題
  • 這三個方法在組織中均有其地位
  • 先把技術性定論放在一邊,確定有助於選擇對各個APP而言適當語言的機制

支持多元化方法的技術正在急速發展

  • 技術創新促進變化
  • HTML5
    • HTML5重視行動體驗的提升
    • 目前還沒有大家同意的最終HTML5標準
    • 組成架構是否會是勝利的基礎
    • 實例分析:The Financial Times
    • HTML5工具及組成架構
    • jQuery Mobile
    • Intel App Framework 2.0
    • Sencha Touch
    • 即使架構本身免費,採用架構也會產生相關的成本
  • Hybrid(混合)開發
  • Native(原生)開發
    • Apple的生態系統
    • Android的生態系統
    • Blackberry的生態系統
    • Windows的生態系統
  • 第4個分類正在出現:Native(原生)跨平台開發

無數要素影響選擇所開發的APP所用語言

  • 選擇以所開發的APP種類為基準
    • 如果重視資料安全性,就開發Native(原生)應用
    • 如果高品質影像不可或缺,Native(原生)應用就具有很大的優勢
    • 大部分企業應用使用HTML就足夠

重視架構及設計將左右應用的成功

  • 不採用架構方式開發者生產性便會降低應用成本升高
  • 加速開發架構方法,將安全及監控簡單化,可節省成本
  • 行動應用程式代理的主要特徵
    • 為了導入分層級架構不需要購買中間套件

建議

  • 給企業的建議
    • 檢討從最初的應用架構到安全性
    • 開發公司內部行動應用程式最初該從HTML5開始
    • 放眼行動應用程式代理技術的發展
    • HTML5幾乎是公司內部應用最好的選擇
    • 絕對不能忘記資料安全性
  • 給供應商的建議
    • 行動應用程式代理是個很大的機會
    • 不要限制您對支援電話及平板電腦方面的野心
    • 設定實用的工具及代理軟體的價格
    • 有三個可用的生態系統,三個都必須注意

附屬資料

  • 相關報告書
  • 調查手法
  • 著者
  • Ovum諮詢
  • 免除責任

圖表

目錄
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.

Highlights

  • 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.

Features Benefits

  • Understand the key differences between the different approaches.
  • Learn about the importance of architecture in successful mobile application development.

Questions Answers

  • 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

Headings

  • SUMMARY
    • Catalyst
    • Ovum view
    • Key messages
    • It is not a question of "which approach," but rather "which approach, when."
    • 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 rapidly
    • Innovation is driving change
    • HTML5
      • 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 given application
    • 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 significant advantage
      • For most enterprise apps, HTML is likely to be more than adequate
  • The emphasis you place on Architecture and design will make or break your application
    • 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 architecture
  • RECOMMENDATIONS
    • Recommendations for enterprises
      • Consider architecture and security from the very first app
      • Your first foray into internally developed mobile applications should be HTML5
      • Watch the evolution of mobile application broker technology
      • For internal applications, HTML5 is nearly always going to be the best bet
      • 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
  • APPENDIX
    • Further reading
    • Author
    • Ovum Consulting
    • Disclaimer

Figures

  • Figure 1: Relative merits of the different approaches
  • Figure 2: Mobile app development "hell"
  • Figure 3: An architectural approach to mobile application development
Back to Top