|
시장보고서
Future of Mobile Content Services
|
Abstract
Say ‘Hello' to the New Mobile Content Industry
- Mobile and Online Programs
- Orange, Vodafone and Verizon
- Google, Yahoo! And Salesforce.com
- Key Success Criteria
- Detailed API Descriptions
- Detailed Future Roadmap
The report begins by describing five successful online open developer
programmes: Yahoo! Search BOSS, Google AppEngine, ebay developer, Amazon Web
Services (AWS) and Saleforce.com AppExchange.
Next, the report reviews a range of equivalent projects that are emanating
from mobile and fixed line telecoms operators: access Orange API, Verizon Open
Developer Initiative (ODI), Vodafone betavine and BT' s Web21c SDK.
The report then compares and contrasts all of these programmes in order to
identify the key success criteria for a successful platform for mobile content
service development. Also included in this part of the report is an analysis
of why the operator' s traditional approach to service development cannot be
maintained in an increasingly complex multi-platform environment.
The report then offers a view of how mobile service development platforms will
evolve in the future by allowing developers to write applications the work
across multiple operator networks and employing APIs that simultaneously offer
programmatic access device assets, mobile network asserts and assets that are
being offered by online players.
Finally, the report offers a detailed description of a technical API that
would offer mobile application developers dramatically more functionality than
anything that exists today. This part of the report also outlines solutions to
the problems of billing and payment, authentication and security.
Who Should Read this Report?
- Product management and product marketing;
- Product strategy and marketing strategy;
- Product, market and network planning;
- Executive leadership;
- Market insight and competitor intelligence;
- Business development and corporate development.
Table of Contents
- Contents
- Synopsis
- Subject Area
- Report Content
- Who Should Read this Report?
- Introduction
- Online Projects
- Yahoo! Search BOSS
- Google AppEngine
- ebay developer
- Amazon Web Services (AWS)
- Salesforce.com AppExchange
- Telecoms Projects
- Orange Partner Programme
- Historic Announcements
- API Features
- Commercial Aspects
- -No Commercialisation Path
- -Onerous Usage Restrictions
- Verizon Open Developer Initiative (ODI)
- Comparison with access Orange API
- Example Market Segments
- Business Rationale
- Business Model Options
- Device Technical Standards
- Activation and Billing Processes
- -Device Activation
- -Billing
- Vodafone betavine
- Example API Features
- Commercial Aspects
- BT Web21C
- Example API Features
- Commercial Aspects
- Other Projects
- Europe
- Asia
- Analysis: Mobile Services
- Historic Model: Mobile Content Service Development
- Need for a New Model
- Slow, labour-intensive, costly process
- Limits Creativity
- Limited API functionality
- Comparison: Online vs. Telecoms Projects
- Senior Management Commitment
- Strong Commercial Focus
- -Project Controlled by Business People
- -Offers Clear Path to Revenue
- -Support Infrastructure
- Competitive Offer
- Evolution of API Models
- Integrated APIs
- -Model 1 API: Device-focused
- -Model 2 API: Network-focused
- -Model 3 API: Device and Network - Integrated
- Cross-network Considerations
- -Cross-network Considerations
- -Converged Services
- Example API: Description
- API Features
- Notification Manager API
- Individual Messaging API
- Group Messaging API
- Inbound Messaging API
- Voice Calling API
- Conference Calling API
- Voice Messaging API
- Location API
- Contact Manager API
- Mapping API
- Browser API
- Data Exchange API
- Application Trigger API
- Media Capture API
- Inter-service Messaging API
- Device Query API
- Customer Data API
- Authentication API
- Billing and Payment
- -Pricing
- -Billing Strategy
- Payment Service Provider Function
- -User Charging
- -Merchant Charging
- -Brand Considerations
|
