Continuing from the last post, let’s talk about the benefits of Eyeline API for end users – developers. Developers are the main drivers behind adoption of APIs, so making sure they get accessible and simple instruments for development is a top priority for mobile operators if they want to make it a profitable business.
Global Mobile Value Added Services Market is expected to grow from $330.35 Billion in 2015 to $655.07 Billion by 2020, at a CAGR of 14.7%, according to a new market research report by Markets & Markets. “The quick innovations in technology have led to the evolution of MVAS beyond the voice communication services. It helps mobile service providers to create and sustain new revenue streams and drive ARPU. Rising mobile phones, network penetration, and increased return on marketing spend are some of the factors driving the mobile value added services market. Social media offer new opportunities for the vendors.”
Rather than concentrating on providing APIs to enterprise and internal developers, it is the time for mobile operators to open opportunities for new talent by means of transparent and functional API. Eyeline API makes development of USSD services truly effortless, as developers no longer need to use complicated SMPP protocol. A service can be created in the form of a site of XML pages with additional functionality programmed in any convenient server side programming language. The second option is used in the cases when the service needs to access databases, perform calculations, make choices depending on user data, etc.
Basic functionality for developers include:
- Quick addition of new providers and implementation of new services. A special module that uses a XML programming language for creating USSD / SMS / Web services is used.
- Build logic service using XML commands. Programming or modification of services can be easily and quickly made by the operator or service provider. It does not require special training. Advertising agencies can begin using the mobile channel promotion almost instantly.
- Complex billing schemes of USSD, SMS, WAP and HTTP traffic. Rules on by billing may take into account user’s personal data, for example, offer discounts based on previous purchases.
In future posts we’ll talk about integration of the API with operator’s infrastructure and billing options. Contact us here if you have questions and stay tuned for more.