Archives

Tagged ‘time to market‘

The trouble with Andriod…

…much like a hitchcock thriller, the case evolves…

A lot is said about the game changing nature of Android, but much doesn’t really make much sense when you start to examine how Android releases are built, released, maintained, and ultimately retired by Google. Some things to note: the tablet market is pretty much owned by iOS, and the Kindle is a touch removed from the Android tree; Gingerbread is the most popular Android release even though the latest versions are supposedly more feature rich and robust; Android is not really free – or at least may not be.

The most interesting debate is currently the Oracle vs Google case, Oracle posted its opening slideshow – here’s a link. Some key slides from it are below – have a look, make of them what you will.

What google copied, apparently quite a bit!

Oh that’s just lawyer talk…isn’t it?

Well, it certainly looks familiar, but hey, in the world where everything is either a zero or a one, some similarity or coincidence is allowed…right?

And of course, its all reusable and shareable, isn’t it?

So its copied, but you can’t share. So its copied to be closed off. Hrumph.

I’ll be interested in seeing what the retort is, but at the moment, none of this is convincing me that if you are an app developer you shouldn’t follow a strategy that is: iOS first, then Android if you must, then if you can be bothered, Windows.

Android Releases – Rapid Updates

With the focus and trend on rapid release cycles and continuous integration underpinning it, it is no surprise to learn that Android has managed to release new versions of its OS ‘rapidly’!

This bodes well for consumers, they get new functions, improved performance and experience, etc. It is challenging for developers and manufacturers, who have to keep up with the OS changes to leverage these benefits in an equally rapid release cycle.

In the end this consumer platform provides value for the consumer through this constant innovation. Is this the future – constantly evolving software or disposable software?

Yahoo! Manhattan…

Yet another cloud, infrastructure as a service, hosting whateverucallit. The names are changing to obscure renditions – google app engine and now manhatten? I still like EC2…sounds like a part of london ;-)

From Wired

Google, Amazon, and Yahoo began life as websites, but they’ve evolved into something more. Now, they share their underlying infrastructure with the outside world, letting other businesses take advantage of the complex hardware and software systems they’ve erected over the years.

Google lets outsiders run applications atop its infrastructure via Google App Engine. Amazon offers its Elastic Compute Cloud (EC2). And sometime next year, Yahoo will launch “Manhattan” — an online service where anyone can build and host applications using standard web technologies such as HTML5 and JavaScript.

Unveiled on Wednesday morning, Manhattan is designed to facilitate the creation of digital magazines and other consumer applications that can be used across a wide variety of devices, from desktops and notebooks to iPads and Android phones.

“We thought about building really cool apps for the iPhone or iPad. But what happens when Android really starts taking off? What happens on web browsers? What happens on feature phones?” Bruno Fernandez-Ruiz, Yahoo vice president, fellow, and chief platform architect, tells Wired.

“So we’ve built a number of things that let you build an application for the Apple App Store, but also distribute the same code to mobile web browsers and browsers on the desktop.”

On Wednesday, Yahoo launched a virtual newsstand atop its site — dubbed Livestand — and Manhattan will provide a means of building digital publications for this service. But developers will also have the freedom to run their apps wherever they like. The only restriction is that applications must be built with standard web technologies.

Early next year, before the arrival of Manhattan, Yahoo will open-source a programming platform dubbed “Mojito.” Based on a widely used open source project known as Node.js, Mojito will allow developers to build entire applications with JavaScript, the web’s standard scripting language. Typically, JavaScript is used to build an application’s front end — the bit that runs on the user’s device — but with Node.js and Mojito, you can also use JavaScript on the back end — the bit that runs on the server.

This also means that Mojito applications can run on devices that are not equipped to run JavaScript. If you’re using a feature phone, for instance, you can still use a Mojito application because the same code can be run on the server side. Yahoo call it Mojito because these application are both “modules” (self-contained application that include everything they need to run on their own) and “widgets” (small applications with an interface designed for quick and easy interaction). “From modules and widgets, we came to ‘mojits,” Fernandez-Ruiz says. “And this became Mojito.”

This, in turn, gave rise to the cocktail theme. Mojito was joined by Manhattan.

You can run these applications on your own servers. But when Manhattan arrives — sometime in 2012 — you’ll also have the option of running them on Yahoo’s infrastructure. This not only frees you from running your own machines; it lets you tap into various other services Yahoo has built for its own site. This includes Yahoo’s CORE technology, which can personalize content for individual users or groups of users, and Yahoo’s ad serving platform.

Unlike Amazon’s EC2 — an “infrastructure cloud” — Manhattan is what’s known as a “platform cloud.” So rather than merely providing raw servers and storage, it provides a higher-level software platform that hides the underlying infrastructure. In this sense, it’s akin to Google App Engine. But whereas App Engine lets you build more complex applications using sophisticated languages like Python and Java, Manhattan handles only HTML5, Javascript, and other standard web tools.

Yahoo is targeting a simpler breed of application. But it’s also working to boost the influence of the web. “Like other web players, we have a fear that the web browser will become obsolete,” says Fernandez-Ruiz. “But by pushing the right standards and making the right tools open source, we think we can solve this problem.”