Ronnie05's Blog

OS and Device agnostic Application platforms

Posted in Applications and User Interfaces, Value added services and applications by Manas Ganguly on February 2, 2011

Openwave (provider of context-aware mediation and messaging solutions) has announced Amplicity, a new browser-based concept, which would deliver apps seamlessly across different OSs and devices in an operator network. This is designed to enable developers to leverage valuable mobile operator network assets to more rapidly create and deliver applications within the browser. The intent is to enable developers to address hardware and software fragmentation through the use of web technologies, including HTML5. In order to improve the distribution process. Developers have always been making an effort to reach out to as many end users and devices as possible. The ability to build one application and have it reach as many users as possible without having to write different versions for different platforms and devices would benefit developers. Operators have always been an essential part of the internet ecosystem, and the data they possess is the key to beating over-the-top players in the battle for consumer mindshare. Openwave Amplicity allows operators to open up their networks to developers and third-party content providers to ultimately create smarter applications that rely on contextual information.

Using Openwave Amplicity, developers will be able to market their applications to consumers and enterprise customers across a number of platforms, which will enable them to monetize these applications through contextual advertising. The Operating System (OS) application development scenario is currently heavily segmented, which poses huge challenges to mobile application developers. Various versions of the same OS keep arriving into the market with continuous development of the platforms, while the developers also find it difficult to design applications compatible with all the mobile devices due to a vast difference in form factors and capabilities of hardware available today. Openwave Amplicity offers a cross-platform footprint based upon HTML-5 to address this issue and provides developers with enhanced OS, hardware and software compatibility. It also offers a more customized browsing experience to the consumers, who will be able to receive contextually relevant advertising and marketing offers on their mobile phones.

Google Gears must die… (for the larger cause)!!

Posted in Computing and Operating Systems, Internet and Search by Manas Ganguly on December 2, 2009

Linus Upson, the man in charge of both the Chrome browser and Chrome OS engineering teams has announced the death of Google Gears. Gears was launched by Google, Mozilla and Opera 3 years back to access web applications offline in browsers. PC Magazine quoted Upson, “We are not driving forward in any meaningful way [on Gears],”. The support wouldnot be drawn out so that applications continue working. Google has been pushing the HTML 5 for some time now. Interestingly as the plot unfolds, Google Gears was the precursor of HTML 5, literally and figuratively.

Quoting Upson “When we started the Gears project, three years ago… we did it because we couldn’t get the browser vendors interested in building offline applications.” He then details the mind trick: Google ships Gears, and suddenly browser vendors are “very interested in adding capabilities to build offline applications,” paving the way for the capabilities in the next version of HTML. Clever, Google. In the same interview, Upson stated the company’s plans to move all its apps to standards-based HTML 5 APIs”. Neat trick Google!!!

Much of the technology in Gears, including offline support and geolocation APIs, are being incorporated into the HTML5 spec as an open standard supported across browsers, and that is the logical next step for developers looking to include these features in their websites.Google is now pushing developers to use HTML5 for these features moving forward as it’s a standards-based approach that will be available across all browsers. The company wants to push HTML5 so that people use it to write web apps that match the quality of the native apps for its two emergent platforms: Android and Chrome OS.

Why HTML5 for Google?

Reason 1:
Google’s biggest problem with both of these mobile-oriented operating systems is that it has to work with hardware partners, which makes it difficult for the company to maintain a tight control on the ecosystem. Motorola, HTC, Sony Ericsson and Samsung have all come out with their own interfaces for the Android, which is already causing some developer dissatisfaction. Against such a backdrop, it makes perfect sense for Google to promote web-based apps, because it means there be will a unified experience for end users, regardless of the device (and the platform.)

Reason 2:
Blame Apple: As admitted by CEO Eric Schmidt, Google needs the open internet to take the fight to Apple in the apps space. While Apple builds up its path to the next big platform: The Superphone, it has effectively kept the Apps Store out of Google’s reach. Thus Apple is making the Mobile Apps device stationary.Google on the other hand is trying to put the apps on the internet with easy access such that it can access user activity in order to serve more targeted advertising. HTML 5 is Google’s weapon and key access to internet led apps activity. With web apps, Google can not only continue to have access to user data (public not private), it can also continue to serve advertising to those users. For developers, it would mean embedding Google ads in their web apps.

Thus the full story: Google Gears kindles interest in Offline Applications. It builds scale for HTML 5 to take over. HTML 5 serves Google’s dual need to make platform uniform and serve up ads to application heavy consumers.

Kudos to the thought and Google’s plan, except for one small thing: Web apps will need better wireless networks with much lower latency and higher bandwidth capabilities in order to meet (and beat) the native apps.

%d bloggers like this: