Enyo 2.1.1 updated for Internet Explorer 10 touch and Kindle Fire HD | webOS Nation

Enyo 2.1.1 updated for Internet Explorer 10 touch and Kindle Fire HD 5

by Derek Kessler Thu, 29 Nov 2012 5:02 pm EST

Enyo 2.1.1 supports Internet Explorer 10 touch and Kindle Fire HD

The platform-agnostic Enyo application framework is expanding its reach, adding support for Internet Explorer 10 touch events and Amazon's new Kindle Fire HD platform. IE 10 itself is a multi-platform browser, operating on Windows Phone 8, Windows 8/Windows RT, and Windows 7. Enyo has from the start been able to handle both touch and mouse pointer events across every platform it supports (of which there are many), but with the update to 2.1.1, Enyo apps can take advantage of IE 10's new Pointer Event API. HP's Enyo team has also been working on implementing support for deploying your Enyo-based apps into the Windows Store on Windows 8, as well as watching the progress of PhoneGap has made towards support of Windows Phone 8.

The 2.1.1 update also improves support for the Kindle Fire HD, having successfully "ironed out" a few "quirks" introduced by the new version of Amazon's Silk browser on the new tablet. As such, The Kindle Fire HD and IE 10 have joined the Tier-1 support level for Enyo 2.x, joining Chrome, Safari, Firefox, IE9 and 8, Android 2.3 and 4.x, iOS 5 and 6, and Open webOS.

The update for Enyo 2.1.1 is relatively minor (unless you're really into developing apps for Windows 8), but Enyo 2.2 is around the corner with a more substantial update: an optional MVC library. In the coming week or so, the Enyo team plans on inviting developers to check out a preview release for Enyo 2.2, so if you're interested you're being advised to "keep your eye on the [Enyo] forums and the enyo-dev mailing list" for the relevant details.

Source: The Enyo Blog


Excellent, so who is using this to dev WebOS Apps? anyone? Can Apps for iOS / Android be easily made into WebOS apps if developed with Enyo, If so why is there very little appearing in our App Store?

Seems to me that the WebOS eco-system is about to run out of momentum, and the combined fanboy power that we have (and I still rock a Pre 3), is not doing anything but keeping the memory alive!

There's a very real danger that Enyo will not be relevant to WebOS unless devs use it to make WebOS Apps.

Agree / Disagree ?

Can apps for iOS / Android be easily made into webOS apps if developed with Enyo 2? Look at the supported platforms
webOS is in tier 2 (supported at lower priority), so that must be possible with some difficulties, but in mobile app development nothing is easy.
Android 4+ (PhoneGap) and iOS 5+ (PhoneGap) are in tier 1 (supported at high priority) but that wasn't your question.
open webOS will be in tier 1, too.

The only people that have made iOS and Android apps with Enyo are former and current webOS developers porting their apps to other platforms. There's literally no Enyo app out there that was built specifically for iOS or Android...unless someone knows something the rest of the world doesn't.
The problem is:
1) Most developers for other platforms use their native SDKs in order to fully and immediately leverage the capabilities of the platform, instead of relying on PhoneGap (which Enyo needs). PhoneGap is almost always behind by a full version from iOS because they need to update their codebase each and every time a new iOS version comes out in order to catch up with its featureset when it can. And still it can't support everything.
2) Even if the developer decides not to use the native SDKs, there are are already a great number of other frameworks that are more robust and offer much more flexibility. Appcelerator Titanium, PhoneGap w/jQuery Mobile, Sencha Touch, etc. And because of the giant communities behind each of those, that's where the development mindshare goes.
Enyo has as much an uphill climb to build that community as Open webOS does when it comes to being successful. Right now, they're both young projects but the competition is already entrenched, highly robust, and have massive communities.
(Ironically, jQuery Mobile actually supports more of webOS in its top tier alone than Enyo does through all of its tiers.)
This is why you aren't seeing an avalanche of Enyo-based apps on webOS, much less other platforms. On the latter, nobody's building them right now. It's that simple.

I tried myself to write and install a proof-of-concept app (not a complete app) on my Android device, and discovered that Enyo 2 does NOT need PhoneGap on Android (I don't know about iOS). You can use a WebView (a View that displays web pages) instead.
Enyo 2 is available under the Apache v2 license, which is very good.
And it's fast and lightweight.
You're right, it's a young project, but it has some potential.

unfortunately, I concur!

Great Idea, just about 2 years too late. Maybe 3 .