First open source Enyo app jumping to other platforms: Paper Mache on Android, FlashCards everywhere | webOS Nation
 
 

First open source Enyo app jumping to other platforms: Paper Mache on Android, FlashCards everywhere 9

by Derek Kessler Wed, 25 Jan 2012 3:57 pm EST

That was fast. It's like HP was working with developers on making this happen or something. The very first webOS app based on open source Enyo getting used on another platform has arrived, and it's our favorite Instapaper client Paper Mache. Developer Ryan Watkins has taken advantage of the now entirely open source nature of the Enyo application framework and used it to release his app into the Android Market. Designed to work on Android 2.2 and higher, Paper Mache brings the full Enyo interface to Android-powered phones and tablets. And, just as with the webOS version, it's free.

Also taking advantage of the open sourcing of Enyo is James Harris of FlashCards fame. The popular webOS study app saw an Enyo release on the TouchPad a few months ago and now thanks to Enyo open source is available in all WebKit browsers and via the Chrome Web Store. The WebKit web app means you can use FlashCards in browsers like Chrome and Safari, but also with on mobile browsers like those found on the iPad and Android tablets.

Enyo's gone open source and the developers have already gone wild. By making the application framework open source and web compatible, HP's ensuring the future of the framework and making it that much easier to justify developing for webOS. Build once, deploy everywhere.

9 Comments

James Harris is the author of FlashCards ;)

Writing too fast! *fixed*

Awesome! But what is the HP plan to avoid fragmentation of open webOS? Isn't this the crucial factor?

What everyone thinks of when they hear fragmentation is the Android problem with apps being incapable of running on some phones. This *should* be less of a problem with apps made using HTML5, but then it'll still be a problem on Android since OEM's have custom implementations of Android and subsequently Webkit. As long as anyone who eventually makes webOS devices uses a relatively recent version of Webkit, it won't be too much of a problem. Running Enyo apps on Android, though, which suffers from carriers and manufacturers delaying in releasing updated versions of Android, would be more of a problem.

More likely, he's had this waiting in the wings. If HP worked with some developers behind the scenes, I'll be really disappointed, since I must've missed that forum post or something.

Maybe these individuals just knew about Enyo going OSS at the same time as everyone else and realized what it meant. They then probably got to work right away and had this ready to go when the time came instead of sitting around complaining.

But it's just a guess, I wouldn't know...

Well thanks, jerk. I didn't know this would be announced today. I know a lot of developers already were working on cross-platform via PhoneGap, etc. and had their work "waiting in the wings". This was in response to "It's like HP was working with developers on making this happen", which made it sound like some developers had priority, which would not be cool.

But thanks for accusing me of complaining. Real classy, jerk.

What a great reward for webOS developers who stuck with our platform! In the recent past, to focus on webOS solely meant losing out on more profitable financial markets like iOS and Android. Finally something that can be disruptive to iOS and Android lock on mobile market!

How is it going to be disruptive to iOS and Android? Both Android and iOS currently support HTML 5 so developers have had this available to them for quite some time. In that regards, Enyo is "just another framework". It doesn't do anything special along the current trend which is to make native rather than web apps. If you look at numbers from sources like comScore, they still show that mobile users are migrating towards native apps rather than mobile websites.

Both native and mobile web remain important, but like I said, mobile web has had pretty mature tools for quite some time. At the end of the day, the stuff built on Enyo will likely be used mostly on iOS and Android; sort of the opposite of disruptive, no?