表紙
市場調査レポート

通信対応アプリ・コンテンツ・コマース市場の予測:WebRTC・通信事業者によるAPI・モバイルアプリ (2015-2020年)

Communication Enabled Applications, Content, and Commerce: WebRTC, Telecom APIs, and Mobile Apps 2015 - 2020

発行 Mind Commerce 商品コード 345954
出版日 ページ情報 英文 455 Pages
納期: 即日から翌営業日
価格
本日の銀行送金レート: 1USD=101.51円で換算しております。
Back to Top
通信対応アプリ・コンテンツ・コマース市場の予測:WebRTC・通信事業者によるAPI・モバイルアプリ (2015-2020年) Communication Enabled Applications, Content, and Commerce: WebRTC, Telecom APIs, and Mobile Apps 2015 - 2020
出版日: 2015年12月02日 ページ情報: 英文 455 Pages
概要

当レポートでは、WebRTC、通信事業者によるAPI、モバイルアプリケーションのコンバージェンスの動向について包括的に調査し、技術およびソリューションの概要、特徴、利用事例、バリューチェーン、競合・協力関係、各社の戦略および各種取り組み、世界および地域別の市場成長予測、市場成長への各種影響因子の分析、将来の展望、市場機会、関連事業者への提言などをまとめています。

ウェブリアルタイム通信:世界・地域のWebRTCソフトウェア・アプリケーション・サービス・ソリューション・デバイス市場の予測

第1章 イントロダクション

第2章 WebRTCとWebRTC市場の概要

  • WebRTCについて
  • WebRTCの進化
  • WebRTCソリューション市場
  • WebRTC市場の影響因子
  • WebRTCのエコシステム/バリューチェーン

第3章 WebRTCの分類

  • WebRTCの各種技術
    • ネイティブアプリ vs WebRTC
    • HTML5
    • WebRTCと4G/LTEによるメディア/データ利用の拡張
    • LTE/4G・RCS・WebRTC
    • キャリアWIFIとWebRTC
    • クラウド通信とWebRTC
    • オープンソースAPIとWebRTC
  • WebRTCアーキテクチャ
  • WebRTCの機能性
  • WebRTCエンタープライズアプリケーション
  • WebRTC API
    • SDP
    • ORCA
    • WebRTCセキュリティ
    • CHROME
    • FIREFOX
    • メディアストリーム (GetUserData)
    • HOOKFLASH
    • メディアストリームAPI
    • RTCデータチャネルAPI
  • クラウドRTCプラットフォーム

第4章 WebRTCアプリケーション事例

  • WebRTCアプリケーションの製作工程
  • WebRTCアプリケーション
  • WebRTCの利用事例
  • WebRTCのエコノミクス

第5章 WebRTCソリューション市場の予測

  • 世界市場の益予測
  • 収益予測:地域別
  • WebRTC収益予測:ソリューション・サービス別
  • WebRTCサービス区分の収益予測
  • WebRTC収益予測:産業別
  • 導入モデル別の収益予測
  • WebRTC収益予測:主要アプリケーションカテゴリー別
  • 世界のWebRTCデバイスの予測
  • WebRTCデバイスの予測:地域別
  • 世界のWebRTCアクティブユーザー数の予測
  • WebRTCアクティブユーザー数の予測:地域別
  • CSPによる世界のWebRTCアクティブユーザー数の予測

第6章 通信事業者・CSPの役割

  • キャリア統合
  • 非キャリア提携
  • 通信メディエーター
  • 通信事業者による付加価値サービス (VAS)
  • 新しいビジネスモデルと市場機会
  • 通信事業者によるAPI
  • CSPの役割

第7章 WebRTCベンダー環境

  • 総市場の競合環境
    • プラットフォームベンダー
    • 音声ソリューションベンダー
    • ビデオソリューションベンダー
    • カンファレンスソリューションプロバイダー
    • 通信WebRTCキャリア
    • オンプレミスベンダー
    • OTT通信プロバイダー
    • バルクSMSベンダー
    • 学習・開発ベンダー
  • ALCATEL LUCENT
  • AT&T
  • AVAYA
  • CAFEX
  • CISCO SYSTEMS
  • DIALOGIC
  • ERICSSON
  • GENBAND
  • GOOGLE
  • HUAWEI TECHNOLOGIES
  • IBM CORPORATION
  • ORACLE
  • PLIVO
  • QUOBIS
  • SONUS
  • TEMASYS
  • TOKBOX TELEFONICA
  • TWILIO

第8章 WebRTCの将来性

  • 音声/ビデオ・ブラウザを超えて:WebRTCとCDN
  • ハイブリッドP2P・サーバーベースのCDN
  • 新しいWebRTCの課題と市場機会
  • WebRTC実装の状況
  • マシンラーニング・5GにおけるWebRTCアプリケーション

第9章 提言

通信事業者によるAPI市場:戦略・エコシステム・事業者・市場予測

第1章 イントロダクション

第2章 通信事業者によるAPI:概要

  • ネットワークAPIの定義
  • 通信APIのキャリアによる導入の理由
  • 通信事業者によるAPIのカテゴリー
    • ウェブリアルタイム通信 (WebRTC)
    • SMS・RCS-E
    • プレゼンス
    • MMS
    • 位置情報
    • 決済
    • 音声/話者
    • 音声制御
    • マルチメディア音声制御
    • M2M
    • SDM/ID管理
    • 加入者プロファイル
    • QoS
    • ID/SSO
    • コンテンツデリバリー
    • ホステッドUC
    • ディレクトリ
    • ナンバープロビジョニング
    • USSD
    • 非デジタルグッズのビリング
    • 広告
    • コラボレーション
    • IVR/音声ストア
  • 通信事業者によるAPIビジネスモデル
  • 市場区分
  • 競合上の課題
  • APIを利用するアプリケーションの割合
  • 通信事業者によるAPIの収益の可能性
  • 通信事業者によるAPI利用:産業部門別
  • 通信事業者によるAPIのバリューチェーン
  • 各種APIトランザクションのコスト
  • APIトランザクションのボリューム

第3章 APIアグリゲーション

  • APIアグリゲーターの役割
  • アグリゲーターによるAPI利用の総コスト
  • アグリゲーターによるAPI利用:カテゴリー別

第4章 エンタープライズ・通信事業者によるAPIの市場

  • DaaS
  • API市場メーカー
  • 新しいタイプのアプリケーション市場の必要性:CAM
    • 通信対応アプリケーション市場 (CAM)
    • CAM市場の市場機会と課題

第5章 通信事業者によるAPI対応アプリの利用事例

  • 通信対応アプリの収益化
    • 直接API収益
    • データの収益化
    • コスト削減
    • 利用拡大
    • 解約削減
  • 利用事例と課題
    • セキュリティ
    • 相互運用性

第6章 非通信事業者によるAPIとマッシュアップ

  • 非通信事業者によるAPI
    • Twitter
    • Netflix API
    • Google Maps
    • Facebook
    • YouTube
    • Flickr
    • eBay
    • Last.fm
    • Amazon Web Service
    • Bing Maps
    • Yahoo Web Search API
    • Shopping.com
    • Salesforce.com
  • マッシュアップ
    • BBC News on Mobile
    • GenSMS emailSMS
    • Foursquare
    • Amazon SNS and Nexmo
    • Triage.me
    • MappyHealth
    • Lunchflock
    • Mobile Time Tracking
    • Fitsquare
    • GeoSMS
    • FONFinder
    • Pound Docs
    • 140Call
    • Salesforce SMS

第7章 キャリア戦略

  • キャリアの市場略戸位置付け
    • API投資の拡大
    • SDM
    • 通信事業者によるAPI標準化
    • キャリアのAPIへの意識
  • 世界のキャリアAPIプログラム
    • AT&T Mobility
    • Verizon Wireless
    • Vodafone
    • France Telecom
    • Telefonica
  • キャリア・通信事業者内部によるAPI利用
    • 内部利用の事例
    • 通信事業者内部によるAPIの利用事例
  • キャリア・OTTサービスプロバイダー
    • OTTプロバイダーによるアプリケーション管理
    • キャリアのAPIを収益化するための革新的スキルの不足
  • キャリアと付加価値サービス (VAS)
    • VASの役割と重要性
    • キャリアによる通信対応VASの事例
    • 課題と市場機会

第8章 API対応アプリ開発業者の戦略

  • 開発業者の重要資産
  • APIリリースの成長の刺激
  • キャリアプログラムに沿った作業
  • 開発業者の好み:Google vs キャリア

第9章 通信APIベンダー戦略

  • 通信API企業・ソリューション
    • Alcatel Lucent
    • UnboundID
    • Twilio
    • LOC-AID
    • Placecast
    • Samsung
    • AT&T Mobility
    • Apigee
    • 2600 Hz
    • Callfire
    • Plivo
    • Tropo (now part of Cisco)
    • Urban Airship
    • Voxeo (now Aspect Software)
    • TeleStax
    • Intel

第10章 市場分析・予測

  • 通信事業者によるAPI収益の予測
  • 通信事業者によるAPI収益の予測:APIカテゴリー別
    • メッセージングAPIの収益
    • LBS APIの収益
    • SDM APIの収益
    • 決済APIの収益
    • IoT APIの収益
    • その他のAPIの収益
  • 通信API収益の予測:地域別

第11章 将来のAPI市場の成長に向けた技術・市場の推進因子

  • SOA
  • SDN
  • 仮想化
  • IoT

第12章 専門家の見解:TeleStax

第13章 専門家の見解:Twilio

第14章 専門家の見解:Point.io

第15章 専門家の見解:Nexmo

第16章 付録

モバイルアプリケーション市場:市場分析・今後の発展と市場機会に関する評価

第1章 イントロダクション

第2章 モバイルアプリケーションの概要

第3章 モバイルプラットフォーム (OS)

  • OHA Android (フリー&オープンソース)
  • iOS:Apple
  • BlackBerry 10:RIM
  • Windows Mobile:Microsoft
  • BlackBerry OS:RIM
  • BREW:Qualcomm
  • Symbian OS:Nokia and Accenture
  • Firefox OS:Mozilla Foundation
  • Sailfish OS:Jolla
  • TIZEN:the Linuz Foundation
  • Ubuntu:Canonical Ltd.

第4章 モバイルプログラミング

  • ウィジェット
  • ハードウェアウィジェット
  • ハードウェア・ソフトウェアの進化
    • ハードウェアの進化・端末製造業者の市場シェア
    • スマートフォンの進化
    • 開発プラットフォーム
    • HTML5
    • HTML・ミニブラウザ
    • Adobe・Flash・SilverLight
    • JavaScript
    • AJAX
    • モバイル開発の将来の方向性

第5章 アプリケーション開発プラットフォーム

  • J2ME プラットフォーム
  • プラットフォーム固有の開発ツール
    • iOS SDK
    • Blackberry OS
    • Nokia
    • Motorola
    • LG
    • Samsung
    • HTC
    • Sony Ericsson
    • Android

第6章 主要な開発コンセプト

  • モバイル開発の動向
    • プラットフォーム
    • プログラミング技術
    • モバイルでの最適化
    • ソフトウェア開発手法
  • ネイティブプログラミング技術
    • サイズの制約
    • ディスプレイの制約
    • 入力・制御
  • ネットワークアクセス

第7章 モバイルアプリケーション市場

  • モバイル広告
  • 市場サマリー

第8章 アプリケーションストアのケーススタディ

  • Blackberry (RIM)
  • Apple
  • Android
  • Amazon App Store
  • Windows App Store

第9章 市場規模

  • モバイルアプリケーションの総市場
  • モバイル売上の潜在性
  • スマートフォン売上の予測
  • 成長指標
  • 市場分析
  • アプリケーションストア市場の実績

第10章 モバイルゲームアナリティクス

第11章 ウェアラブルデバイスアプリと将来のアプリ

  • フィットネスアプリ
  • ウェアラブルデバイスの決済アプリ
  • 将来のウェアラブルアプリ

第12章 キャリア・ベンダーによる適合

  • トポロジー・ネットワークの変更
  • 複数のプラットフォームのモバイルOS

第13章 アプリケーションパブリッシャーの分析

  • Gameloft
  • GungHo Online
  • Electronic Arts
  • Zynga
  • DeNA
  • SEGA
  • King

第14章 モバイルアプリケーションの将来性

  • 通信タイプアプリ
  • 組込みエンターテインメント&ゲーミフィケーションアプリ
  • クロスプラットフォームアプリ
  • SMACの影響
目次

Overview:

During this unprecedented time of change for legacy communication service providers (CSP), network operators must leverage new technologies and solutions to provide next generation applications to meet the challenge from non-traditional CSPs, Over-the-Top (OTT) service providers, and other competitors. Web Real-time Communications (WebRTC) is one tool in the toolkit along with Telecom APIs and integration with carrier and OTT apps for a greatly enhanced and blended service experience.

Mind Commerce sees an emerging Telecom API enabled marketplace that will leverage incumbent CSP data to enhance enterprise services and consumer applications for both third-parties as well as value-added services for carriers themselves. This new marketplace will allow network operators to monetize raw data assets in a Data-as-as-Service (DaaS) model as well as add value to an emerging new class of WebRTC enabled services that will benefit greatly from both carrier data as well as third-party data integration.

This research represents the most comprehensive analysis focused on this convergence of WebRTC, Telecom APIs, and mobile applications. It includes technology evaluation, solution assessment, company analysis and forecasts for each area from 2015 to 2020. All purchases of Mind Commerce reports includes time with an expert analyst who will help you link key findings in the report to the business issues you're addressing. This needs to be used within three months of purchasing the report.

Target Audience:

  • WebRTC companies
  • Mobile API providers
  • Mobile VAS companies
  • Mobile device manufacturers
  • Application stores/aggregators
  • Cloud application management companies
  • Mobile network operators and their partners
  • Mobile VAS application development companies

Table of Contents

Web Real-time Communications: WebRTC Software, Applications, Services, Solutions, and Devices Market with Global and Regional Forecast 2015 - 2020

1.0. INTRODUCTION

  • 1.1. EXECUTIVE SUMMARY
  • 1.2. TARGET AUDIENCE
  • 1.3. COMPANIES IN REPORT

2.0. WEBRTC AND WEBRTC MARKET OVERVIEW

  • 2.1. UNDERSTANDING WEBRTC
    • 2.1.1. WEBRTC FEATURES
    • 2.1.2. WEBRTC ADVANTAGES
    • 2.1.3. PEER TO PEER VS. BROWSER TO BROWSER COMMUNICATION
    • 2.1.4. CLICK TO CALL
  • 2.2. EVOLUTION OF WEBRTC
  • 2.3. WEBRTC SOLUTION MARKET
  • 2.4. WEBRTC MARKET FACTORS
    • 2.4.1. GROWTH DRIVERS
    • 2.4.2. MARKET LIMITATIONS
    • 2.4.3. MARKET OPPORTUNITIES
  • 2.5. WEBRTC ECOSYSTEM / VALUE CHAIN
    • 2.5.1. VENDORS
    • 2.5.2. PRODUCTS
    • 2.5.3. SOLUTIONS AND SERVICES
    • 2.5.4. APPLICATIONS
    • 2.5.5. DELIVERY PLATFORMS
    • 2.5.6. END USERS

3.0. WEBRTC TAXONOMY

  • 3.1. WEBRTC TECHNOLOGY
    • 3.1.1. NATIVE APPS VS. WEBRTC
    • 3.1.2. HTML5
    • 3.1.3. WEBRTC AND EXPANSION OF MEDIA/DATA USAGE VIA 4G/LTE
    • 3.1.4. LTE/4G, RCS, AND WEBRTC
    • 3.1.5. CARRIER WIFI AND WEBRTC
    • 3.1.6. CLOUD COMMUNICATION AND WEBRTC
    • 3.1.7. OPEN SOURCE API AND WEBRTC
  • 3.2. WEBRTC ARCHITECTURE
  • 3.3. WEBRTC FUNCTIONALITY
    • 3.3.1. VOICE CALLING 2
    • 3.3.2. REAL TIME MESSAGING
  • 3.4. WEBRTC ENTERPRISE APPLICATION
    • 3.4.1. CUSTOMER FACING ENTERPRISE
    • 3.4.2. IN-HOUSE LICENSES DEVELOPMENT
    • 3.4.3. APPLICATION AND SECURITY
  • 3.5. WEBRTC API
    • 3.5.1. SESSION DESCRIPTION PROTOCOL (SDP)
    • 3.5.2. OPEN REAL-TIME COMMUNICATIONS API (ORCA)
    • 3.5.3. WEBRTC SECURITY
    • 3.5.4. CHROME
    • 3.5.5. FIREFOX
    • 3.5.6. MEDIA STREAM (GETUSERDATA)
    • 3.5.7. HOOKFLASH
    • 3.5.8. MEDIASTREAM API
    • 3.5.9. RTCDATACHANNEL API
  • 3.6. CLOUD RTC PLATFORM

4.0. WEBRTC APPLICATION CASES

  • 4.1. STAGES OF CREATION OF WEBRTC APPLICATION
    • 4.1.1. GETTING STARTED
    • 4.1.2. CREATING VIDEO AUDIO CALLING
    • 4.1.3. USING TEXT
    • 4.1.4. FILE SHARING
  • 4.2. WEBRTC APPLICATIONS
    • 4.2.1. USE OF WEBRTC IN E-LEARNING
    • 4.2.2. WEBRTC IN CORPORATE MEETINGS
    • 4.2.3. WEBRTC AND HTML5 DEVELOPMENTS
    • 4.2.4. WEBRTC FOR THE MOBILE APPLICATIONS
  • 4.3. WEBRTC USE CASES
    • 4.3.1. CUSTOMER CARE
    • 4.3.2. PREMIUM CUSTOMER SERVICES
    • 4.3.3. CUSTOMER WILLINGNESS TO PAY FOR SUCH PREMIUM SERVICES
  • 4.4. ECONOMICS OF WEBRTC

5.0. WEBRTC SOLUTION MARKET FORECAST 2015 - 2020

  • 5.1. GLOBAL MARKET REVENUE FORECAST 2015 - 2020
  • 5.2. REGION WISE REVENUE FORECAST 2015 - 2020
    • 5.2.1. NORTH AMERICA COUNTRY WISE REVENUE FORECAST 2015 - 2020
    • 5.2.2. WESTERN EUROPE COUNTRY WISE REVENUE FORECAST 2015 - 2020
    • 5.2.3. APAC COUNTRY WISE REVENUE FORECAST 2015 - 2020
    • 5.2.4. EASTERN EUROPE COUNTRY WISE REVENUE FORECAST 2015 - 2020
    • 5.2.5. LATIN AMERICA COUNTRY WISE REVENUE FORECAST 2015 - 2020
    • 5.2.6. MIDDLE EAST & AFRICA COUNTRY WISE REVENUE FORECAST 2015 - 2020
  • 5.3. WEBRTC REVENUE FORECAST BY SOLUTION AND SERVICE 2015 - 2020
  • 5.4. WEBRTC SERVICE SEGMENT REVENUE FORECAST 2015 - 2020
  • 5.5. WEBRTC REVENUE FORECAST BY INDUSTRY VERTICAL 2015 - 2020
  • 5.6. DEPLOYMENT MODEL WISE REVENUE FORECAST 2015 - 2020
  • 5.7. WEBRTC REVENUE FORECAST BY MAJOR APPLICATION CATEGORY 2015 - 2020
  • 5.8. GLOBAL WEBRTC DEVICE FORECAST 2015 - 2020
  • 5.9. WEBRTC DEVICE FORECAST BY REGION 2015 - 2020
  • 5.10. GLOBAL WEBRTC ACTIVE USER FORECAST 2015 - 2020
  • 5.11. WEBRTC ACTIVE USER FORECAST BY REGION 2015 - 2020
    • 5.11.1. NORTH AMERICA WEBRTC ACTIVE USER FORECAST 2015 - 2020
    • 5.11.2. WESTERN EUROPE WEBRTC ACTIVE USER FORECAST 2015 - 2020
    • 5.11.3. APAC WEBRTC ACTIVE USER FORECAST 2015 - 2020
    • 5.11.4. EASTERN EUROPE WEBRTC ACTIVE USER FORECAST 2015 - 2020
    • 5.11.5. LATIN AMERICA WEBRTC ACTIVE USER FORECAST 2015 - 2020
    • 5.11.6. MIDDLE EAST & AFRICA WEBRTC ACTIVE USER FORECAST 2015 - 2020
  • 5.12. CSP DRIVEN GLOBAL WEBRTC ACTIVE USER 2015. - 2020

6.0. ROLE OF TELECOM OPERATORS AND CSPS

  • 6.1. CARRIER INTEGRATION
  • 6.2. NON-CARRIER PARTNERSHIPS
  • 6.3. COMMUNICATION MEDIATOR
  • 6.4. TELECOM VALUE-ADDED SERVICES (VAS)
  • 6.5. NEW BUSINESS MODELS AND OPPORTUNITIES
    • 6.5.1. TELEFONICA CASE STUDY
    • 6.5.2. ANOTHER POTENTIAL FOR CSPS: WEBRTC AND TOLL-FREE CALLING
  • 6.6. TELECOM API
  • 6.7. ROLE OF CSPS

7.0. WEBRTC VENDOR LANDSCAPE

  • 7.1. OVERALL COMPETITIVE LANDSCAPE
    • 7.1.1. PLATFORM VENDORS
    • 7.1.2. VOICE SOLUTION VENDORS
    • 7.1.3. VIDEO SOLUTION VENDORS
    • 7.1.4. CONFERENCE SOLUTION PROVIDERS
    • 7.1.5. TELECOM WEBRTC CARRIER
    • 7.1.6. ON-PREMISE VENDORS
    • 7.1.7. OTT COMMUNICATION PROVIDERS
    • 7.1.8. BULK SMS VENDORS
    • 7.1.9. LEARNING AND DEVELOPMENT VENDORS
  • 7.2. ALCATEL LUCENT
    • 7.2.1. OVERVIEW
    • 7.2.2. ANALYSIS
  • 7.3. AT&T
    • 7.3.1. OVERVIEW
    • 7.3.2. ANALYSIS
  • 7.4. AVAYA
    • 7.4.1. OVERVIEW
    • 7.4.2. ANALYSIS
  • 7.5. CAFEX
    • 7.5.1. OVERVIEW
    • 7.5.2. ANALYSIS
  • 7.6. CISCO SYSTEMS
    • 7.6.1. OVERVIEW
    • 7.6.2. ANALYSIS
  • 7.7. DIALOGIC
    • 7.7.1. OVERVIEW
    • 7.7.2. SWOT ANALYSIS
  • 7.8. ERICSSON
    • 7.8.1. OVERVIEW
    • 7.8.2. ANALYSIS
  • 7.9. GENBAND
    • 7.9.1. OVERVIEW
    • 7.9.2. ANALYSIS
  • 7.10. GOOGLE
    • 7.10.1. OVERVIEW
    • 7.10.2. ANALYSIS
  • 7.11. HUAWEI TECHNOLOGIES
    • 7.11.1. OVERVIEW
    • 7.11.2. ANALYSIS
  • 7.12. IBM CORPORATION
    • 7.12.1. OVERVIEW
    • 7.12.2. SWOT ANALYSIS
    • 7.13. MITEL NETWORKS
    • 7.13.1. OVERVIEW
    • 7.13.2. ANALYSIS
  • 7.14. ORACLE
    • 7.14.1. OVERVIEW
    • 7.14.2. ANALYSIS
  • 7.15. PLIVO
    • 7.15.1. OVERVIEW
    • 7.15.2. ANALYSIS
  • 7.16. QUOBIS
    • 7.16.1. OVERVIEW
    • 7.16.2. SWOT ANALYSIS
  • 7.17. SONUS
    • 7.17.1. OVERVIEW
    • 7.17.2. ANALYSIS
  • 7.18. TEMASYS
    • 7.18.1. OVERVIEW
    • 7.18.2. ANALYSIS
  • 7.19. TOKBOX TELEFONICA
    • 7.19.1. OVERVIEW
    • 7.19.2. ANALYSIS
  • 7.20. TWILIO
    • 7.20.1. OVERVIEW
    • 7.20.2. ANALYSIS

8.0. FUTURE OF WEBRTC

  • 8.1. BEYOND VOICE/VIDEO AND BROWSERS: WEBRTC AND CDNS
  • 8.2. HYBRID P2P AND SERVER-BASED CDN
  • 8.3. EMERGING WEBRTC ISSUES AND OPPORTUNITIES
  • 8.4. WEBRTC IMPLEMENTATION STATUS
  • 8.5. WEBRTC APPLICATIONS IN MACHINE LEARNING AND 5G

9.0. RECOMMENDATIONS

  • 9.1. COMMUNICATION SERVICE PROVIDERS
  • 9.2. SOCIAL MEDIA COMPANIES
  • 9.3. CONTENT PROVIDERS
  • 9.4. APPLICATION DEVELOPERS
  • 9.5. COMMERCE PROVIDERS
  • 9.6. INFRASTRUCTURE PROVIDERS
  • 9.7. DEVICE MANUFACTURERS

Figures

  • Figure 1: WebRTC Framework
  • Figure 2: WebRTC Value Chain / Ecosystem (from Vendor to End User)
  • Figure 3: WebRTC Architecture
  • Figure 4: Video Calling using WebRTC Applications
  • Figure 5: WebRTC Global Market Revenue Forecast $ Million 2015 - 2020
  • Figure 6: WebRTC Market Revenue Forecast by Region $ Million 2015 - 2020
  • Figure 7: WebRTC Market Share by Region 2015 - 2020
  • Figure 8: North America Revenue Forecast by Country $ Million 2015 - 2020
  • Figure 9: Western Europe Revenue Forecast by Country $ Million 2015 - 2020
  • Figure 10: APAC Revenue Forecast by Country $ Million 2015 - 2020
  • Figure 11: Eastern Europe Revenue Forecast by Country $ Million 2015 - 2020
  • Figure 12: Latin America Revenue Forecast by Country 2015 - 2020
  • Figure 13: Middle East and Africa Revenue Forecast by Country 2015 - 2020
  • Figure 14: WebRTC Revenue Forecast Solution vs. Service $ Million 2015 - 2020
  • Figure 15: WebRTC Market Share Solution vs. Service Vertical 2015 - 2020
  • Figure 16: WebRTC Revenue Forecast by Service Segment $ Million 2015 - 2020
  • Figure 17: WebRTC Revenue Forecast by Industry Vertical $ Million 2015 - 2020
  • Figure 18: WebRTC Revenue Forecast by Deployment Model $ Million 2015 - 2020
  • Figure 19: WebRTC Revenue Forecast by App Category $ Million 2015 - 2020
  • Figure 20: Global WebRTC Enabled Device Forecast in Billion 2015 - 2020
  • Figure 21: WebRTC Enabled Device Forecast by Region in Billion 2015 - 2020
  • Figure 22: WebRTC Enabled Device Share by Region 2015 - 2020
  • Figure 23: Global WebRTC Active User Forecast in Billion 2015 - 2020
  • Figure 24: WebRTC Active Users by Region in Million 2015 - 2020
  • Figure 25: WebRTC Active Users Share by Region 2015 - 2020
  • Figure 26: WebRTC Active Users North America in Million 2015 - 2020
  • Figure 27: WebRTC Active Users Western Europe in Million 2015 - 2020
  • Figure 28: WebRTC Active Users APAC in Million 2015 - 2020
  • Figure 29: WebRTC Active Users Eastern Europe in Million 2015 - 2020
  • Figure 30: WebRTC Active Users Latin America in Million 2015 - 2020
  • Figure 31: WebRTC Active Users ME & Africa in Million 2015 - 2020
  • Figure 32: Carrier Driven Global WebRTC Active Users Million 2015 - 2020
  • Figure 33: WebRTC and IMS Integration Structure
  • Figure 34: New Business Model in WebRTC Carrier Ecosystem
  • Figure 35: WebRTC Vendor Competitive Landscape
  • Figure 36: Avaya WebRTC Ecosystem Diagram
  • Figure 37: Genband SPiDR Gateway
  • Figure 38: Oracle WebRTC Session Controller
  • Figure 39: Sippo WebRTC Application Controller Diagram
  • Figure 40: WebRTC Progress by Browswer Type
  • Figure 41: WebRTC at the Center of Coms, Apps, Content, and Commerce

Telecom API Marketplace: Strategy, Ecosystem, Players and Forecasts 2015 - 2020

1. Introduction

  • 1.1. Executive Summary
  • 1.2. Topics Covered
  • 1.3. Key Findings
  • 1.4. Target Audience
  • 1.5. Companies Mentioned

2. Telecom Network API Overview

  • 2.1. Defining Network APIs
  • 2.2. Why Carriers are Adopting Telecom Network APIs
    • 2.2.1. Need for New Revenue Sources
    • 2.2.2. B2B Services and Asymmetric Business Models
  • 2.3. Telecom Network API Categories
    • 2.3.1. Web Real-time Communications (WebRTC)
    • 2.3.2. SMS and RCS-E
    • 2.3.3. Presence
    • 2.3.4. MMS
    • 2.3.5. Location
    • 2.3.6. Payments
    • 2.3.7. Voice/Speech
    • 2.3.8. Voice Control
    • 2.3.9. Multimedia Voice Control
    • 2.3.10. M2M
    • 2.3.11. SDM/Identity Management
    • 2.3.12. Subscriber Profile
    • 2.3.13. QoS
    • 2.3.14. ID/SSO
    • 2.3.15. Content Delivery
    • 2.3.16. Hosted UC
    • 2.3.17. Directory
    • 2.3.18. Number Provisioning
    • 2.3.19. USSD
    • 2.3.20. Billing of Non-Digital Goods
    • 2.3.21. Advertising
    • 2.3.22. Collaboration
    • 2.3.23. IVR/Voice Store
  • 2.4. Telecom Network API Business Models
    • 2.4.1. Two-Sided Business Model
    • 2.4.2. Exposing APIs to Developers
    • 2.4.3. Web Mash-ups
  • 2.5. Segmentation
    • 2.5.1. Users by Segment
    • 2.5.2. Workforce Management
  • 2.6. Competitive Issues
    • 2.6.1. Reduced TCO
    • 2.6.2. Open APIs
    • 2.6.3. Configurability
  • 2.7. Percentage of Applications that use APIs
  • 2.8. Telecom API Revenue Potential
    • 2.8.1. Standalone API Revenue vs. Finished Goods Revenue
    • 2.8.2. Telecom API-enabled Mobile VAS Applications
    • 2.8.3. Carrier Focus on Telecom API's for the Enterprise
  • 2.9. Telecom Network API Usage by Industry Segment
  • 2.10. Telecom Network API Value Chain
    • 2.10.1. Telecom API Value Chain
    • 2.10.2. How the Value Chain Evolve
    • 2.10.3. API Transaction Value Split among Players
  • 2.11. Cost for Different API Transactions
  • 2.12. Volume of API Transactions

3. API Aggregation

  • 3.1. The Role of API Aggregators
  • 3.2. Total Cost Usage for APIs with Aggregators
    • 3.2.1. Start-up Costs
    • 3.2.2. Transaction Costs
    • 3.2.3. Ongoing Maintenance/Support
    • 3.2.4. Professional Services by Intermediaries
  • 3.3. Aggregator API Usage by Category
    • 3.3.1. An LBS Case Study: LOC-AID
    • 3.3.2. Aggregation: Intersection of Two Big Needs
    • 3.3.3. The Case for Other API Categories
    • 3.3.4. Moving Towards New Business Models

4. Enterprise and Telecom API Marketplace

  • 4.1. Data as a Service (DaaS)
    • 4.1.1. Carrier Structured and Unstructured Data
    • 4.1.2. Carrier Data Management in DaaS
    • 4.1.3. Data Federation in the DaaS Ecosystem
  • 4.2. API Market Makers
    • 4.2.1. mashape
    • 4.2.2. Mulesoft
  • 4.3. Need for a New Type of Application Marketplace: CAM
    • 4.3.1. Communications-enabled App Marketplace (CAM)
    • 4.3.2. CAM Market Opportunities and Challenges

5. Telecom API Enabled App Use Cases

  • 5.1. Monetization of Communications-enabled Apps
    • 5.1.1. Direct API Revenue
    • 5.1.2. Data Monetization
    • 5.1.3. Cost Savings
    • 5.1.4. Higher Usage
    • 5.1.5. Churn Reduction
  • 5.2. Use Case Issues
    • 5.2.1. Security
    • 5.2.2. Interoperability

6. Non-Telecom Network APIs and Mash-ups

  • 6.1. Non-Telecom Network APIs
    • 6.1.1. Twitter
    • 6.1.2. Netflix API
    • 6.1.3. Google Maps
    • 6.1.4. Facebook
    • 6.1.5. YouTube
    • 6.1.6. Flickr
    • 6.1.7. eBay
    • 6.1.8. Last.fm
    • 6.1.9. Amazon Web Services
    • 6.1.10. Bing Maps
    • 6.1.11. Yahoo Web Search API
    • 6.1.12. Shopping.com
    • 6.1.13. Salesforce.com
  • 6.2. Mash-ups
    • 6.2.1. BBC News on Mobile
    • 6.2.2. GenSMS emailSMS
    • 6.2.3. Foursquare
    • 6.2.4. Amazon SNS and Nexmo
    • 6.2.5. Triage.me
    • 6.2.6. MappyHealth
    • 6.2.7. Lunchflock
    • 6.2.8. Mobile Time Tracking
    • 6.2.9. Fitsquare
    • 6.2.10. GeoSMS
    • 6.2.11. FONFinder
    • 6.2.12. Pound Docs
    • 6.2.13. 140Call
    • 6.2.14. Salesforce SMS

7. Carrier Strategies

  • 7.1. Carrier Market Strategy and Positioning
    • 7.1.1. Increasing API Investments
    • 7.1.2. The Rise of SDM
    • 7.1.3. Telecom API Standardization
    • 7.1.4. Carrier Attitudes towards APIs: U.S vs. Asia Pacific and Western Europe
  • 7.2. Carrier API Programs Worldwide
    • 7.2.1. AT&T Mobility
    • 7.2.2. Verizon Wireless
    • 7.2.3. Vodafone
    • 7.2.4. France Telecom
    • 7.2.5. Telefonica
  • 7.3. Carriers and Internal Telecom API Usage
    • 7.3.1. The Case for Internal Usage
    • 7.3.2. Internal Telecom API Use Cases
  • 7.4. Carriers and OTT Service Providers
    • 7.4.1. Allowing OTT Providers to Manage Applications
    • 7.4.2. Carriers Lack the Innovative Skills to Capitalize on APIs Alone
  • 7.5. Carriers and Value-added Services (VAS)
    • 7.5.1. The Role and Importance of VAS
    • 7.5.2. The Case for Carrier Communication-enabled VAS
    • 7.5.3. Challenges and Opportunities for Carriers in VAS

8. API enabled App Developer Strategies

  • 8.1. A Critical Asset to Developers
  • 8.2. Stimulating the Growth of API Releases
  • 8.3. Working alongside Carrier Programs
  • 8.4. Developer Preferences: Google vs Carriers

9. Telecom API Vendor Strategies

  • 9.1. Positioning as Enablers in the Value Chain
  • 9.2. Moving Away from a Box/Product Supplier Strategy
  • 9.3. Telecom API Companies and Solutions
    • 9.3.1. Alcatel Lucent
    • 9.3.2. UnboundID
    • 9.3.3. Twilio
    • 9.3.4. LOC-AID
    • 9.3.5. Placecast
    • 9.3.6. Samsung
    • 9.3.7. AT&T Mobility
    • 9.3.8. Apigee
    • 9.3.9. 2600 Hz
    • 9.3.10. Callfire
    • 9.3.11. Plivo
    • 9.3.12. Tropo (now part of Cisco)
    • 9.3.13. Urban Airship
    • 9.3.14. Voxeo (now Aspect Software)
    • 9.3.15. TeleStax
    • 9.3.16. Intel
    • 9.3.17. Competitive Differentiation

10. Market Analysis and Forecasts

  • 10.1. Telecom Network API Revenue 2015 - 2020
  • 10.2. Telecom Network APIs Revenue by API Category 2015 - 2020
    • 10.2.1. Messaging API Revenues
    • 10.2.2. LBS API Revenues
    • 10.2.3. SDM API Revenues
    • 10.2.4. Payment API Revenues
    • 10.2.5. Internet of Things (IoT) API Revenues
    • 10.2.6. Other API Revenues
  • 10.3. Telecom API Revenue by Region 2015 - 2020
    • 10.3.1. Asia Pacific
    • 10.3.2. Eastern Europe
    • 10.3.3. Latin & Central America
    • 10.3.4. Middle East & Africa
    • 10.3.5. North America
    • 10.3.6. Western Europe

11. Technology and Market Drivers for Future API Market Growth

  • 11.1. Service Oriented Architecture (SOA)
  • 11.2. Software Defined Networks (SDN)
  • 11.3. Virtualization
    • 11.3.1. Network Function Virtualization (NFV)
    • 11.3.2. Virtualization beyond Network Functions
  • 11.4. The Internet of Things (IoT)
    • 11.4.1. IoT Definition
    • 11.4.2. IoT Technologies
    • 11.4.3. IoT Applications
    • 11.4.4. IoT Solutions
    • 11.4.5. IoT, DaaS, and APIs (Telecom and Enterprise)

12. Expert Opinion: TeleStax

13. Expert Opinion: Twilio

14. Expert Opinion: Point.io

15. Expert Opinion: Nexmo

16. Appendix

  • 16.1. Research Methodology
  • 16.2. Telecom API Definitions
  • 16.3. More on Telecom APIs and DaaS
    • 16.3.1. Tiered Data Focus
    • 16.3.2. Value-based Pricing
    • 16.3.3. Open Development Environment
    • 16.3.4. Specific Strategies
      • 16.3.4.1. Service Ecosystem and Platforms
      • 16.3.4.2. Bringing to Together Multiple Sources for Mash-ups
      • 16.3.4.3. Developing Value-added Services (VAS) as Proof Points
      • 16.3.4.4. Open Access to all Entities including Competitors
      • 16.3.4.5. Prepare for Big Opportunities with the Internet of Things (IoT)

Figures

  • Figure 1: Wireless Carrier Assets
  • Figure 2: Telecom API: Standalone vs. Finished Services
  • Figure 3: RCS and Telecom API Integration
  • Figure 4: RCS Revenue Forecast
  • Figure 5: Business vs. Consumer Telecom API Focus
  • Figure 6: Enterprise Dashboard
  • Figure 7: Enterprise Dashboard App Example
  • Figure 8: Telecom Network API Value Chain
  • Figure 9: Value Split among Aggregators, Carriers and Enterprise for API Transactions: 2012 - 2019
  • Figure 10: API Transaction Costs (US Cents) 2012 - 2019
  • Figure 11: Volume of API Transactions for a Tier 1 Carrier (Billions per Month): 2015 - 2020
  • Figure 12: Cloud Services and APIs
  • Figure 13: GSMA OneAPI: Benefits to Stakeholders
  • Figure 14: AT&T Wireless API Catalog
  • Figure 15: Verizon Wireless API Program
  • Figure 16: France Telecom (Orange) APIs
  • Figure 17: Telefonica APIs
  • Figure 18: Carrier Internal Use of Telecom APIs
  • Figure 19: UnboundID's Portfolio of Services
  • Figure 20: Twilio's Portfolio of Services
  • Figure 21: LOC-AID Exchange Server Architecture
  • Figure 22: Placecast's ShopAlerts Solution
  • Figure 23: Apigee Portfolio of Services
  • Figure 24: Telecom API Revenue (USD Billions) 2015 - 2020
  • Figure 25: Telecom API Revenue (USD Billions) by API Category 2015 - 2020
  • Figure 26: Messaging APIs Revenue (USD Billions) 2015 - 2020
  • Figure 27: LBS APIs Revenue (USD Billions) 2015 - 2020
  • Figure 28: SDM APIs Revenue (USD Billions) 2015 - 2020
  • Figure 29: Payment APIs Revenue (USD Billions) 2015 - 2020
  • Figure 30: IoT API Revenue (USD Billions) 2015 - 2020
  • Figure 31: APIs Revenue for Other Categories (USD Billions) 2015 - 2020
  • Figure 32: Telecom API Revenue (USD Billions) by Region 2015 - 2020
  • Figure 33: Telecom API Revenue (USD Billions) Asia Pacific 2015 - 2020
  • Figure 34: Telecom API Revenue (USD Billions) Eastern Europe 2015 - 2020
  • Figure 35: Telecom API Revenue (USD Billions) Latin & Central America 2015 - 2020
  • Figure 36: Telecom API Revenue (USD Billions) Middle East & Africa 2015 - 2020
  • Figure 37: Telecom API Revenue (USD Billions) North America 2015 - 2020
  • Figure 38: Telecom API Revenue (USD Billions) Western Europe 2015 - 2020
  • Figure 39: Services Oriented Architecture
  • Figure 40: Growth of Connected Devices
  • Figure 41: IoT and Telecom API Topology
  • Figure 42: Telestax App Store Funnel
  • Figure 43: On-Premise vs. Twilio
  • Figure 44: Point.io and API Ecosystem
  • Figure 45: Different Data Types and Functions in DaaS
  • Figure 46: Ecosystem and Platform Model
  • Figure 47: Telecom API and Internet of Things Mediation
  • Figure 48: DaaS and IoT Mediation for Smartgrid

Mobile Application Marketplace 2015: Market Analysis and Assessment of Future Evolution and Opportunities

1. Introduction

  • 1.1. Executive Summary
  • 1.2. Target Audience
  • 1.3. Companies Mentioned

2. Mobile Applications Overview

  • 2.1. Definition of a Mobile Applications
  • 2.2. What Separates an App From a Bundled Device Feature?
  • 2.3. Examples of Current Mobile Apps

3. Mobile Platforms (Operating Systems)

  • 3.1. OHA Android (free and open source)
  • 3.2. iOS from Apple
  • 3.3. BlackBerry 10 from RIM
  • 3.4. Windows Mobile from Microsoft
  • 3.5. BlackBerry OS from RIM
  • 3.6. BREW from Qualcomm
  • 3.7. Symbian OS from Nokia and Accenture
  • 3.8. Firefox OS from Mozilla Foundation
  • 3.9. Sailfish OS from Jolla
  • 3.10. TIZEN from the Linuz Foundation
  • 3.11. Ubuntu from Canonical Ltd.

4. Mobile Programming

  • 4.1. Widgets
  • 4.2. Hardware Widgets
  • 4.3. Hardware and Software Evolution
    • 4.3.1. Hardware Evolution and Handset Manufacturers Market Share
    • 4.3.2. The Smartphone Revolution
    • 4.3.3. Development Platforms
    • 4.3.4. HTML5
    • 4.3.5. HTML and Mini Browsers
    • 4.3.6. Adobe, Flash, and SilverLight
    • 4.3.7. JavaScript
    • 4.3.8. AJAX
    • 4.3.9. Future Directions of Mobile Development

5. Application Development Platforms

  • 5.1. J2ME Platform
  • 5.2. Platform Specific
    • 5.2.1. iOS SDK
    • 5.2.2. Blackberry OS Development Tools
    • 5.2.3. Nokia Development Tools
    • 5.2.4. Motorola Development Tools
    • 5.2.5. LG Development Tools
    • 5.2.6. Samsung Development Tools
    • 5.2.7. HTC Development Tools
    • 5.2.8. Sony Ericsson Development Tools
    • 5.2.9. Android Development Tools

6. Key Development Concepts

  • 6.1. Mobile Development Trends
    • 6.1.1. Platforms
    • 6.1.2. Programming Techniques
    • 6.1.3. Mobile Optimization
    • 6.1.4. Software Development Methodology
  • 6.2. Native Programming Techniques
    • 6.2.1. Size Constraints
      • 6.2.1.1. Compact Code
      • 6.2.1.2. Compact File Space
    • 6.2.2. Display Constraints
      • 6.2.2.1. Display Sizes and Standards
      • 6.2.2.2. Multiple Displays
    • 6.2.3. Input and Controls
      • 6.2.3.1. Input device types
      • 6.2.3.2. Keyboard
      • 6.2.3.3. Touch Screen
      • 6.2.3.4. Thumb Sticks, Roller Balls, and Direction Pads
      • 6.2.3.5. Environmental Controls
      • 6.2.3.6. Motion and Orientation Sensors
      • 6.2.3.7. Light Sensors
      • 6.2.3.8. Proximity Sensor
      • 6.2.3.9. Gyroscope
      • 6.2.3.10. Accelerometer
      • 6.2.3.11. Peripheral Access
      • 6.2.3.12. GPS Onboard and Off
      • 6.2.3.13. Bluetooth
      • 6.2.3.14. Near Field Communication and S Beam
      • 6.2.3.15. Touch ID
      • 6.2.3.16. Stylus Pen
  • 6.3. Network Access
    • 6.3.1. Connection Persistence
    • 6.3.2. Dial on Demand
    • 6.3.3. Always On
    • 6.3.4. Connection Types and Limitations
    • 6.3.5. Cellular Data
    • 6.3.6. WiFi
    • 6.3.7. Bluetooth
    • 6.3.8. Bluetooth Low Energy (BLE)
    • 6.3.9. Processing
    • 6.3.10. Platforms and Speeds

7. Mobile Application Market

  • 7.1. Mobile Advertising
  • 7.2. Market Summary

8. Application Store Case Studies

  • 8.1. Case Study Blackberry (RIM)
  • 8.2. Case Study Apple
  • 8.3. Case Study Android
  • 8.4. Case Study: Amazon App Store
  • 8.5. Case Study Windows App Store

9. Market Size

  • 9.1. Mobile Application Overall Market
  • 9.2. Mobile Sales Potential
  • 9.3. Forecasted Smart Phone Sales
  • 9.4. Growth Indicators
  • 9.5. Market Analysis
  • 9.6. Application Store Market Performance
    • 9.6.1. Apple App Store
    • 9.6.2. Android Marketplace Analysis

10. Mobile Gaming Analytics

  • 10.1.1. Monetizing Micro Transaction in F2P Model: Creating a Need Approach is Key
  • 10.1.2. Game Balancing Method in Micro Transaction Model
  • 10.1.3. Potential Risk and Solution in F2P Virtual Economy
  • 10.1.4. Pricing Decision Factors: ARPU vs. Average game price vs. Average Gamers
  • 10.1.5. Product Life Cycle of Mobile Game: Adoption of Moore's Lifecycle Model
  • 10.1.6. Game Lifecycle KPI framework
  • 10.1.7. Smartphones vs. Portable Game Players

11. Wearable Devices Apps and Future Apps

  • 11.1. Fitness Apps
  • 11.2. Wearable Devices Payment Apps
  • 11.3. Future Wearables Apps
    • 11.3.1. Military Applications
    • 11.3.2. Industry and Enterprise Applications
    • 11.3.3. A Day in the Life of a Celebrity App
    • 11.3.4. In my Glass

12. Carrier and Vendor Adaptations

  • 12.1. Topology and Network Changes
    • 12.1.1. Policy Changes
    • 12.1.2. Open Network Movements
    • 12.1.3. Billing Plan Changes
    • 12.1.4. Infrastructure Hardware Changes
    • 12.1.5. Location Based Services
    • 12.1.6. WiFi Localized Service Hosting
    • 12.1.7. Handset Manufacturer Changes
    • 12.1.8. Integrating New Handset Features
    • 12.1.9. Evolving the Handset
  • 12.1.10. Multiple Platform Mobile Operating Systems

13. App Publishers Analysis

  • 13.1. Gameloft
  • 13.2. GungHo Online
  • 13.3. Electronic Arts
  • 13.4. Zynga
  • 13.5. DeNA
  • 13.6. SEGA
  • 13.7. King

14. Future of Mobile Applications

  • 14.1. Communication Enabled Apps
    • 14.1.1. Direct API Revenue
    • 14.1.2. Data Monetization
    • 14.1.3. Cost Savings
    • 14.1.4. Higher Usage
    • 14.1.5. Churn Reduction
  • 14.2. Embedded Entertainment and Gamified Apps
    • 14.2.1. Gamification
    • 14.2.2. Wearable Gamification
    • 14.2.3. Mobile Social Gamification
    • 14.2.4. Cloud Gamification
  • 14.3. Cross Platform Apps
    • 14.3.1. Smartphones, Tablets, Wearable Tech and More
    • 14.3.2. Mobile/Wireless Apps Everywhere
  • 14.4. The Impact of SMAC
    • 14.4.1. Social, Mobile, Analytics, and Cloud (SMAC)
    • 14.4.2. SMAC Stack
    • 14.4.3. SMAC and Enterprise Mobile Market and Apps

Tables

  • Table 1: Example of the Most Successful Apps
  • Table 2: Apps Revenues in Apple App and Google Play Stores
  • Table 3: Handsets Manufacturer Market Share
  • Table 4: Mobile/Tablet Browser Share
  • Table 5: Mobile Platform Market Share 2012 - 2020
  • Table 6: Smartphone Market SWOT
  • Table 7: Key Considerable Mobile Gaming Strategies
  • Table 8: Mobile Gaming Business Model Descriptions
  • Table 9 Game Balancing Methods in Virtual Economy
  • Table 10: Potential Risk & Solution in F2P Virtual Economy
  • Table 11: Revenue vs. Costs in Gaming App Business
  • Table 12: Gameloft most Successful Apps
  • Table 13: Gungho Online Entertainment, Inc most Successful Apps
  • Table 14: EA most Successful Apps
  • Table 15: Zynga most Successful Apps
  • Table 16: DeNa Most Successful Apps
  • Table 17: SEGA Most Successful App
  • Table 18: King Applications

Figures

  • Figure 1: iPhone 6 and iPhone 6 Plus
  • Figure 2: iOS 8
  • Figure 3: Windows Phone 8 from Nokia
  • Figure 4: BlackBerry Z10
  • Figure 5: First Mobile Widgets
  • Figure 6: Early Mobile Widgets and Hardware
  • Figure 7: The Rise of the Smartphones Era
  • Figure 8: Classic Web App vs. Ajax Web Application Model
  • Figure 9: Samsung Note Edge
  • Figure 10: Multi-touch Screen
  • Figure 11: Touch ID
  • Figure 12: Blackberry OS 10.1
  • Figure 13: Amazon App Store
  • Figure 14: Apple App Store vs. iTunes Music Sales
  • Figure 15: Mobile Gaming Business Models
  • Figure 16: Monetizing Micro-Transaction in F2P model
  • Figure 17: Adoption of Moore's Lifecycle Model in Mobile Gaming
  • Figure 18: Sequential Steps of Mobile Game Analytic Approach
  • Figure 19: Mobile Game Lifecycle KPI Framework
  • Figure 20: Apple Watch Payments using NFC
  • Figure 21: A Day in a Life of a Celebrity
  • Figure 22: Mobile App Store Framework
Back to Top