Mobile Applications

Download 0.56 Mb.
bet	3/3
Sana	26.12.2019
Hajmi	0.56 Mb.
	#5262

Bu sahifa navigatsiya:

• Figure 1: OneAPI scheme

The TechWatch Secretariat is interested in your ideas for mobile applications related to ITU, ITU-T Recommendations, etc. Which is your preferred mobile platform, and what kind of information about ITU would you like to be able to retrieve using your smartphone? Please send your comments, ideas and suggestions to tsbtechwatch@itu.int and join the Technology Watch Correspondence Group, at http://www.itu.int/ITU-T/techwatch/cg.html. Image: “P1i Outside” at Flickr. Uploaded by topgold.

In most cases, apps are programmed by third party developers. However, they remain subject to approval by store owners (in many cases, such as Apple, by the phone manufacturer itself) that take care of distribution, payment and limited marketing of the product, in return for some 30 per cent of the sales price of each application.
Since the billing system, rating by users and marketing mechanisms are common for thousands of apps, online stores represent a potentially highly profitable activity for their owners (see also “The Long Tail”⁴). The latest upgrade of the iPhone OS (3.0) extends this approach to microcommerce, allowing developers to sell premium content or services within their apps, using the store to collect one-off or subscription fees.⁵ Mobile marketing in the form of branded applications and in-application advertising is starting to take off and promising additional revenues.⁶ In addition, the software store business is a facilitator of hardware sales.
Rejection of a third party app can be triggered by objectionable content (e.g., obscenity) or duplication of functions contained in those bundled with the device. Some network operators fear “cannibalization” of existing services from new functionalities and therefore restrict applications such as:

• 
  VoIP apps that challenge conventional voice calls (e.g., Skype⁷);
  
• 
  IM (Instant Messaging) apps that challenge SMS; and
  
• 
  Apps that would speed-up surfing and limit online traffic.
  
  
  

These, together with the fear of malware (malicious software), make vendors hesitant to allow developers direct access to the core functionalities of a device, including the phone module, the web browser, the email client and the media player.
Restrictions by manufacturers, vendors and providers have led to a practice, which for the iPhone became known as jailbreaking. After the installation of an unofficial software patch, users can bypass the official app distribution mechanism, and install unapproved grey-market applications. For instance, the application iPhoneModem⁸ allows the phone to share its Internet connection with a PC or Mac. Until recently, Apple did not approve Internet sharing applications.⁹ Generally, jailbreaking a device voids manufacturer warranty.
Variations and/or ambiguity in these manufacturer restrictions and the lack of interoperability between platforms are obstacles to development of the mobile apps market. Apps written by developers for one device must be rewritten, since application programming interfaces (API) and software development kits (SDK) are specific to each of the major platforms. This process slows time to market, limits market size, prevents customers from using purchased apps on devices of a different type, and causes customer confusion about availability and features.
However, the differences between mobile platforms seem to disappear in some areas. The open source WebKit browser engine¹⁰ that concentrates some of the latest technologies for web browsers is the basis for most mobile web browsers; the API of OpenGL ES¹¹, a standard for graphics for embedded systems, is now widely used to address the graphics hardware of mobile devices.
Backed by the popularity of its founding member Google, the Open Handset Alliance (OHA) is a group of 47 companies whose stated purpose is a commitment to greater openness in the mobile ecosystem.¹² Its flagship is the open source Linux-based mobile platform Android, which is already showing signs of rapid adoption by manufacturers, operators, application developers and users¹³, and is now to be found on some netbooks and other devices, including in-vehicle infotainment systems.¹⁴ Even before consumer devices equipped with Android were available, thousands of app developers jumped into this market, hoping to be ready for the launch of the first Android devices.

Available on some 30 different handset models, the LiMo Platform (Linux Mobile) is an open operating system for use by the whole mobile industry. The LiMo Foundation was founded by NEC, NTT docomo, Orange, Panasonic, Samsung and Vodafone, and has expanded to more than 50 international members.¹⁵

Figure 1: OneAPI scheme



Source: GSMA 3rd Party Access Project – OneAPI, https://gsma.securespsite.com/access/.

Another industry forum, the Open Mobile Terminal Platform (OMTP) aims at “simplifying the customer experience of mobile data services and improving mobile device security.”¹⁶ It recently published the BONDI specification, which defines interfaces for secure access to the core functionalities of a device from its web browser or user interface. This avoids developers being locked into one particular platform and enables them to write applications for all BONDI capable handsets.

The GSM Association’s OneAPI initiative¹⁷ seeks to define a commonly supported API to allow operators to disclose information about and capabilities of their mobile network to app developers. The API supports content creation and apps that are portable across the networks of different operators, and provide common interfaces for messaging, location, user data, connection and charging (see Figure 1). The initiative also aims at working with standards bodies on the needs of developers for APIs.

ITU has contributed to the considerable success of mobile communications and applications, including through its role as the global manager of the radio-frequency spectrum, publisher of the IMT-2000 family of standards (3G) and pioneer of IMT-Advanced standards (Beyond 3G). A unique international mobile subscriber identity (IMSI) conforming to ITU-T E.212 is stored in each SIM card and used for identification when interconnecting between (mobile) networks. Many handsets carry implementations of ITU-T Recommendations, for example, speech and audio codecs, such as G.718 or G.722.2, multimedia decoders for H.263 and H.264 or conform to handset specifications in ITU-T P.300 series of Recommendations.¹⁸

Software developers are demanding lightweight standards and interfaces, which are easily understood and adopted in their applications. In the field of multimedia, accessibility, hands-free communication/user-interfaces and mobile television are areas to keep an eye on. Also, the fusion of communications and location offers potential applications and (location-based) services far beyond automotive navigation systems. Finally, the challenge continues for mobile network operators, service providers and their customers to find solutions to user authentication, identity management and privacy. These points need to be addressed not only from a technical angle, but also under regulatory and policy perspectives, as laws increasingly obligate mobile operators to fulfill the same functions as fixed-line operators.
ITU estimates that by the end of 2007, about 85 countries worldwide had launched 3G networks, and that by the end of 2008, there were close to 335 million mobile broadband subscribers.¹⁹ To date, mobile broadband uptake is predominantly in the developed world, where penetration has reached 14 per cent, compared to less than one per cent in the developing world. While these trends suggest that developing economies have much catching up to do, technological advances especially in the mobile sector are offering new possibilities and the potential to help more and more people communicate, and to take advantage of mobile apps and services at increasingly high speed.
Increased focus on standards for open and interoperable APIs would contribute to the success of mobile applications.

This ITU-T TechWatch Alert was prepared by Martin Adolph (tsbtechwatch@itu.int). The opinions expressed in this report are those of the author and do not necessarily reflect the views of the International Telecommunication Union or its membership. To find out more about ITU-T’s Technology Watch Function, please visit http://www.itu.int/ITU-T/techwatch.

Download 0.56 Mb.