Machine Learning Authors: Pat Romanski, Liz McMillan, Carmen Gonzalez, Yeshim Deniz, Zakia Bouachraoui

Related Topics: Machine Learning , Agile Computing

Machine Learning : Article

Will "Mobile AJAX" Dominate Web 2.0?

Mobile AJAX Will Replace Both Java ME and XHTML, says Ajit Jaokar

The Possibilities of Mobile AJAX

In spite of the issues mentioned on the previous page, I believe that Ajax will lead to resurgence in browsing applications and will overcome many of the problems we now face because

a) The level of abstraction shifts to the browser. Browser based applications are relatively easier to update and can be used across operators. This leads to a greater target audience for the application. Developers could have access to a critical mass of customers to make application development worthwhile. The browser also reduces fragmentation by providing a universal client(i.e. one client to for all application types as opposed to a separate client for each application type)

b) Ajax is making the browser experience and data management capabilities better

c) Developers are supporting Ajax on the internet and by extension the mobile internet. Industry heavyweights are shifting their support to Ajax(for example IBM’s support for Open Ajax )

d) The concept of widgets is not new. It has been around for some time on the Mac. In this context, a widget is a downloadable, interactive software object that provides a single service such as a map, a news feed etc. Ajax provides a mechanism to implement widgets on browsers.

e) Finally, Ajax could foster the creation of the widget authoring market similar to Apple widgets or Opera widgets

The resurgence of browsing applications is not new. Other bloggers such as Russell Beattie have also spotted the same trend.

However, I believe that Ajax will take it one step further by providing a combination of richer experience, bigger target audience, data management capabilities and widget authoring capabilities.

In addition, the support of developers - both on the web and on the mobile internet - could lead Ajax to morph into a system with greater capabilities than we currently envisage.

Part one of the article was written in context of the Opera platform’s support for Ajax .

As per it’s definition, the Opera Platform comprises:
- Opera web browser running in full-screen mode.
- An AJAX framework for running multiple widgets/applications.
- Access to the phones native functionality through an abstraction layer

Opera already supports AJAX in the 17 million shipped mobile browsers in 2005. This means that - with the existing Opera browsers you can use desktop AJAX services such as GMail, Google Maps etc. This much is quite apparent and has been covered by other analysts before.

However, there is more to the announcement than merely support for Ajax.

The significant elements are

1) The Opera Platform is the first mobile AJAX framework. It also has a corresponding browser framework. However, unlike other frameworks such as Zimbra (zimlets) and Backbase it is fully designed for mobile devices – in the sense that it uses the same codebase on the browser and the mobile device. With minor configuration changes, the desktop/browser widget could also run on the mobile device Thus, from a developer’s perspective, there are more than one ways to monetise the widget(desktop, mobile and browser). This factor, coupled with the large installed base – makes the Opera announcement significant from the mobile applications development standpoint

2) Widgets could call other widgets. Complex applications could thus be developed from simple, browser based components

3) The Opera platform allows access to device APIs
To appreciate this concept, we have to consider the architectural drawbacks of the browser model (corollary ‘a’ as discussed above)

The browser model is document centric i.e. based on mark-up languages. In contrast, downloaded and native applications are application centric since they are based on a programming language.

To be really useful, any mobile applications development model must have the capacity to access data elements that are tightly coupled to the device itself. These include the telephony API, phone book, text messages, the messaging API, call records, the SIM card, the calendar, the Bluetooth stack, media player, the file system and so on.

Applications running on the phone can access these services through APIs. For most part, applications running on browsers could not access these functions(with the exception of a few proprietary solutions).

The opera platform is a browser based programming environment that abstracts the native device APIs through a set of Javascript APIs and thus provides developers access to the low level functions on the device from the browser
This is VERY significant and has the possibility of creating richer browser based applications.

Knowing what we know now about Ajax, widgets etc – lets return back to the example of ‘lawn bowls’.

The power of Ajax lies in it’s ability to create widgets at the desktop level. Using the Opera platform approach, the same widget could be used for the mobile device. These widgets have the ability to harness revenue from the long tail. In the commonwealth games scenario, it should be possible to create a low cost widget catering for the lawn bowls fans. These widgets could run on the desktop browser as well as the mobile browser(using the Opera approach outlined above). There in lies the significance of the Ajax approach!

One would argue that this approach is not a purely browser based approach (because the client in this case needs some form of ‘software’ running locally). Note that – the platform approach is not the same as using a plug-in because a plug-in can be downloaded. In contrast, the platform is a part of the device itself and is installed by the manufacturer.

I agree that this approach is not ‘pure’. However, developers will have to deal with few (perhaps less than ten) such platforms as opposed to the ‘hundreds’ of variants that they have to currently contend with (see notes below).

Nor is this approach ‘open’ – in the sense that an application programmed on one platform will only run on that platform.

Nor is it ‘endorsed’ by OMA as far as I know. The whole issue is still also too early for the mobile operators since it has yet to flow up from browser vendors to the device manufacturers and only then to the operators. However, the W3C mobile web initiative may also be a standards body in this case in collaboration with OMA.

Finally, the approach is still not ‘rich’ enough for certain types of applications such as games( see more on games below).

Nevertheless, it’s a huge step forward because we now have a much more uniform playing field across operators.

Historically, popular technology has often morphed depending on industry support. Take the humble old 'SQL' . Every vendor(such as Sybase, Informix etc) - introduced a procedural version of SQL (PLSQL in case of Oracle). SQL and PLSQL are a contradiction in terms because SQL is set based (and thus by definition not procedural) whereas PLSQL is procedural.

However, ‘procedural’ SQL exists because there was an industry demand (read developer support) behind it. We are witnessing the same phenomenon here with Ajax.

NEXT PAGE: Walled Gardens, Open Gardens in the Context of the Above Approach

More Stories By Ajit Jaokar

Ajit Jaokar is the author of the book 'Mobile Web 2.0' and is also a member of the Web2.0 workgroup. Currently, he plays an advisory role to a number of mobile start-ups in the UK and Scandinavia. He also works with the government and trade missions of a number of countries including South Korea and Ireland. He is a regular speaker at SYS-CON events including AJAXWorld Conference & Expo.

Comments (7)

Share your thoughts on this story.

Add your comment
You must be signed in to add a comment. Sign-in | Register

In accordance with our Comment Policy, we encourage comments that are on topic, relevant and to-the-point. We will remove comments that include profanity, personal attacks, racial slurs, threats of violence, or other inappropriate material that violates our Terms and Conditions, and will block users who make repeated violations. We ask all readers to expect diversity of opinion and to treat one another with dignity and respect.

CloudEXPO Stories
Because Linkerd is a transparent proxy that runs alongside your application, there are no code changes required. It even comes with Prometheus to store the metrics for you and pre-built Grafana dashboards to show exactly what is important for your services - success rate, latency, and throughput. In this session, we'll explain what Linkerd provides for you, demo the installation of Linkerd on Kubernetes and debug a real world problem. We will also dig into what functionality you can build on top of the tools provided by Linkerd such as alerting and autoscaling.
DevOps is a world surrounded by information, starting from a single commit and ending in roll out to production. In this talk, I'll introduce you to the world of Taboola DevOps data collection, to better understand what goes on under the hood. The system we've developed in-house helps us collect and analyse the entire DevOps process from the very first commit all the way to production. It provides us a full clear view with a drill-down toolset that helps keep us away from the dark side. Our KPI's moved from being abstracted ideas to data driven goals, which we can measure and act upon. We're living in a data driven world when all business components are based on our clients action and reaction, why not doing the same thing within our DevOps eco-system?
After years of investments and acquisitions, CloudBlue was created with the goal of building the world's only hyperscale digital platform with an increasingly infinite ecosystem and proven go-to-market services. The result? An unmatched platform that helps customers streamline cloud operations, save time and money, and revolutionize their businesses overnight. Today, the platform operates in more than 45 countries and powers more than 200 of the world's largest cloud marketplaces, managing more than 27 million enterprise cloud subscriptions valued at more than $1 billion in revenue.
In his session at 20th Cloud Expo, Mike Johnston, an infrastructure engineer at Supergiant.io, will discuss how to use Kubernetes to setup a SaaS infrastructure for your business. Mike Johnston is an infrastructure engineer at Supergiant.io with over 12 years of experience designing, deploying, and maintaining server and workstation infrastructure at all scales. He has experience with brick and mortar data centers as well as cloud providers like Digital Ocean, Amazon Web Services, and Rackspace. His expertise is in automating deployment, management, and problem resolution in these environments, allowing his teams to run large transactional applications with high availability and the speed the consumer demands.
Containerized software is riding a wave of growth, according to latest RightScale survey. At Sematext we see this growth trend via our Docker monitoring adoption and via Sematext Docker Agent popularity on Docker Hub, where it crossed 1M+ pulls line. This rapid rise of containers now makes Docker the top DevOps tool among those included in RightScale survey. Overall Docker adoption surged to 35 percent, while Kubernetes adoption doubled, going from 7% in 2016 to 14% percent.