Your browser is not supported. Please update it.

6 October 2011

Amazon and Adobe should come closer to grasp cloud initiative

A year ago, the winners and losers from the mobile world’s eventual shift to HTML5 and cloud services seemed fairly clear, at least at the top level. Google a clear winner, with strong opportunities for Facebook and for HP (brandishing webOS). Adobe a clear loser, Apple strong on technology but with much to lose from the decline of the controlled native environment. Now there are some important shifts, and these could get more significant if two key players, Amazon and Adobe, come closer together.

In creating a powerful back end cloud environment which feeds to its own browser-based device platform, Google is no longer the only game in town with Android and Chrome OS. Amazon has always been a major contender at the back, but has not sought to create an end user experience of its own, except in the ebook market. With the launch of its Kindle Fire tablet, it became clear that the ebook experiment was a dress rehearsal for a far broader content experience, and like Google it will offer its own devices, user interface and browser. Not only has Amazon made its underlying Android OS unrecognizable, but it is challenging Google with its Silk browser, which harnesses cloud-based resources not just to stream content but to make web response faster, going a step beyond the search giant’s Chrome. And the retailer may go even further and develop its own software platform, if it purchases webOS from HP, which is widely rumored.

The other mover in the mobile cloud league table is Adobe, whose promises to evolve for a post-Flash world sounded pretty lame a year ago. Now the company has accepted the inevitable and, while its MAX developer event this week will see updates for Flash and AIR, most of the focus has been on HTML5, the cloud and tablets. With a common interest in influencing the emerging touch-based content experience, as well as a mutual desire to dilute Apple’s impact in this regard, there are many reasons why Amazon and Adobe could become closer friends, especially in the tablet world.

The Kindle Fire, even more than the iPad, is primarily geared to content consumption, not creation, but an increasing amount of that content will be made by amateurs, as the success of YouTube and Amazon’s own self-publishing platform attest. If Adobe can adapt its creative tools for the new cloud/browser world, but also see device makers optimizing their platforms to show off the end result most effectively, it has a chance of remaining relevant even as Flash gets sidelined.

These aims were clear in the release of Touch Apps, cloud-based versions of Adobe’s well established PC family of tools, Creative Suite, adapted for touch-based devices and HTML5. These were a highlight of the start of the MAX event, and it was very clear that they would be good weapons in Amazon’s bid to establish a major base for Kindle Fire, whose raison d”tre is to shift as many cloud services and pieces of digital content as possible. The new tablet is tied into the cloud to a far greater extent than any rival, with much of the firepower of the hugely extensive Amazon Cloud services being directed into the slates. That is one reason why the device can get away with being quite low level in its specs ‘ only 8Gbytes of local storage, because nearly everything is kept remotely; and a browser that does a great deal of its legwork at the back end in order to deliver quick results even to low-powered clients.

Silk is relevant to Adobe not just in a cloud/HTML5 future but because it also supports Flash more richly than most modern tablet browsers. The ‘split browser’ approach carries out all the DNS, TCP/IP connections, handshakes, asset loading and other hefty tasks in the Amazon Cloud, and the browser only has to connect to that to get its content, not to multiple web servers. This will improve the viewing of Flash content as well as HTML5.

That will be valuable in a transition period when Flash and HTML5 will be living alongside one another. Adobe’s task is to allow Flash-like applications to be created using web tools like HTML5 and JavaScript, ensuring that its creative tools still stand out even on the apparently level playing field of the open web. Strong partners are important for that, but so are strong tools themselves, and these were at the heart of the first day at MAX, as was an emphasis on the mobile platforms they would target.

One of Adobe’s missteps with Flash was to take too long to bring full functionality to mobile devices. Instead it gave Apple its weapon by relying on the stripped-down Flash Lite, which ‘ as the iPhone maker always claims ‘ became increasingly inadequate as smartphones became capable of PC-class video. Full Flash Mobile did appear, but only after industry attention was drifting to HTML5 ‘ as shown by the failure of Adobe’s own app store, which was meant to make Flash the main instrument to span the conflicting mobile operating systems. By contrast, the new wave of HTML5-friendly Adobe tools has been designed primarily with mobile devices in mind, and with equivalent functionality across desktop and handset from day one.

The three key elements in this week’s cloud/mobile/web push were Touch Apps, new features for the Edge toolset, and the acquisition of Nitobi, maker of the PhoneGap open source framework, which could smooth Adobe’s transition to its new environment. Touch Apps consists of six programs for Android and iOS tablets, including full Photoshop image editing, but they are only the early fruits of a far broader strategy called Creative Cloud. This will create a hub for viewing, sharing and syncing files created either with Touch Apps or Creative Suite, across multiple platforms. This will be extended over time to allow users to collaborate across a far wider range of devices.

This is not just about migrating between technology platforms, but also changing the revenue model from packaged software fees to the delivery of software online, or as a subscription service. None of the new products will be packaged, and that type of software now accounts for only one-third of Adobe’s sales. ‘The move to the Creative Cloud is a major component in the transformation of Adobe,’ said CTO Kevin Lynch in a statement.

Nitobi Software will also help with that transformation, as an important player in the HTML5 world. Nitobi was a close partner of Nokia in the Symbian days and its PhoneGap framework has been the basis of web developer kits from several mobile players including Sony Ericsson and Palm. Last year, Nitobi announced PhoneGap Build, a cloud-based tool for creating apps in HTML, CSS and JavaScript, uploading them to Build, and getting them back ready to run on various smartphone platforms including Android, iOS, Windows, Symbian, BlackBerry and bada.

Nitobi’s mission has been to increase the number and usability of web-based products for mobile platforms, by making development easier and cheaper, and over time it believes the functions of PhoneGap, and many other cloud-based platforms, will be folded into the browser. The fact that this thinking has landed up inside Adobe shows how rapidly the larger company is evolving to cope with a post-Flash world.

“Our hope is the creative cloud will reach a lot more people than we do today,” added Lynch. “We see this as a way to reach a whole new generation. We are making moves to create new technology ourselves and bring in technologies from others for that purpose as well.”

Indeed, Nitobi and Creative Cloud do seem to offer a far more convincing multiplatform strategy than Adobe’s last one, which was based on the Flash runtime and the packager for iOS (which converts Flash apps, barred from Apple iDevices, to native code). But by allowing HTML5/JavaScript apps to be converted into native apps, PhoneGap will let Adobe free itself of native code and build a standards-based replacement for Flash, which supports any kind of OS.

Adobe has also shown off a third preview release of its Edge web design software, a key element of its Flash-to-HTML migration path. The tool has a built-in WebKit browser and creates animations and graphics through HTML elements styled with CSS 3. End users see a user interface familiar from Flash and After Effects. The latest update features interactivity. This means that effects, such as animation, can be tied to user actions, such as clicking a button on the site. This could be important in highly interactive web apps such as games, and Edge indicates how Adobe is seeking to bring the most sophisticated elements of Flash to its new web strategy. The company acknowledged that Edge cannot yet match Flash for versatility, but it is making steady progress. The new preview release also adds the ability to program using JavaScript as well as relying on pre-written pieces of code. Edge will make its commercial debut next year, initially on PCs and Macs, but with a rapid roadmap to support multiple mobile platforms.

Those might include webOS in future, should that find a new home at Amazon (or elsewhere). Adobe and Nitobi have both worked with the Palm/HP platform before and it does represent one of the most advanced operating systems for the new cloud/browser way of doing things. But since HP backtracked on its plan to put webOS at the heart of a broad cloud device strategy, the product is in limbo, with its phones and tablets killed off, and no clear role in HP’s future. HP has been rumored to be trying to sell the OS, and despite rumors about Samsung, LG and others, the most probable candidate always seemed to be Amazon. The retailer has been creating an increasingly broad-ranging web software platform and even while webOS still remained central to HP’s cloud strategy, the older firm had hinted at a major strategic alliance.

According to VentureBeat, negotiations between the two companies are at an advanced stage, though there may be other interested bidders. There would be clear reasons for Amazon’s interest. The Silk browser is the heart of its new user interface, which currently runs on top of a modified Android, but a fully controlled Linux OS ‘ especially a slimline one well-suited to cloud/browser norms, like webOS ‘ would make sense, freeing it from its somewhat fractious reliance on cloud competitor Google. It would also give it greater freedom to differentiate and control its user experience, and to avoid any legal attacks in future from Apple or Microsoft. For instance, multitasking is very intuitive in webOS.

While having a homegrown OS can be problematic in terms of attracting apps support, as RIM well knows, Amazon’s main focus is on HTML5 web services and particularly on digital media, which are not so OS-sensitive.

HP, meanwhile, has been growing closer to Amazon itself, and Jon Rubinstein, formerly head of Palm, became a board member at the retailer last year. Rubinstein is currently head of product innovation in HP’s Personal Systems Group, which the firm is considering spinning off or selling. In an interview in July, before the cancellation of the Pre and TouchPad devices, he said: “I would say Amazon would certainly make a great partner, because they have a lot of characteristics that would help them expand the webOS ecosystem.”

Rubinstein was said to be hostile to former CEO Leo Apotheker’s bid to license webOS to huge numbers of partners, making it central to the ‘internet of things’. He favored making just one or two partnerships with companies that could add significant value, which would clearly include Amazon. Former webOS division chief Stephen DeWitt also hinted at closer ties with Amazon during the summer. He said: ‘There’s no company on the planet that has more intimacy with their end customers, or knowledge of their end customers. We respect that a lot, and we’ve learned from that. And our partnerships in other areas have taught us a great deal ‘ as a metaphor, that’s the kind of sophisticated partner that makes sense.’