Take a look at Preware 2, as made with Enyo 2 | webOS Nation

Take a look at Preware 2, as made with Enyo 2 21

by Derek Kessler Mon, 11 Mar 2013 4:25 pm EDT

Take a look at Preware 2, as made with Enyo 2

Back in December the WebOS Ports team hosted a virtual hackathon to bring a number of popular and vital webOS homebrew utilities up to modern Enyo 2 standards. Things have been pretty quiet on that front in the intervening month, but last night WebOS Ports developer Josh "@shiftyaxel" Palmer took to Twitter to share screenshots of the progress they've made since.

In short, it's Preware, but built with Enyo. It installs homebrew apps from the webOS Nation Homebrew Gallery and WebOS Internals' own feeds, just as you'd expect. The difference is that by being built with Enyo 2 the app now has a more flexible layout. Typical of the Enyo user interface is the display of multiple columns, with a list of apps on the left side and the selected app's info on the right.

Overall it looks to operate in a similar manner to the Preware we know and love, though Palmer did note that right now Preware 2 will only support Enyo apps on Open webOS installs, as Open webOS doesn't currently offer support for PDK or hybrid apps. That's not to say that Preware 2 can't support PDK-based apps, an IPK is an IPK is an IPK, after all, and older version sof webOS will support PDK and hybrid app installs just fine. Prompted by former webOS developer relations employee Donald Kirker, Palmer pondered that it would be "feasible" to move app installation to a background tasks in Preware 2, conceivably enabling a user to continue browsing apps while installing apps. Consider that more a possibility for future releases, not a promise.

Thanks to its Enyo 2-based status, installation of Preware 2 on varying webOS hardware shouldn't be an issue. Even on older webOS smartphones, the Enyo 2 framework can be packaged with the app at a size under 25KB while still giving cross-platform compatibility and speed. For his part, Palmer's screenshots were taken on a TouchPad running webOS 3.x.

Preware 2 is still in pre-alpha stages and not publicly released, though once they're far enough along the app will be released into the alpha testing feeds in Preware. When that will happen… well, WebOS Ports is very clear on their ETA policy: there are no ETAs - when it's ready, it's ready. So hold on, check out the screenshots after the break, and dream of someday going all Enyo for your homebrew fun.

Preware 2

Preware 2

Preware 2


This looks amazing! Great work and a heartfelt thank you to Josh Palmer from the community!

I concur, great work team! Can't wait to take it for a spin :D

Looking awesome! Can't wait to try it!

If only there were apps to fill up this sweet looking app browser.

I'm thinking it would be nice if this appeared as an example on the Enyo site.

Interested developers could see what can be done with Enyo - including building the entire app-catalogue itself! I think it would be a great showcase and incentive.

I assume that though limited on OwOS, the finished work could offer the full range of apps on current devices.

Excellent work!

What's the incentive here? I really don't see any inherent "incentive" for developers in this new release as great as it is to see webOS Internals chugging along in the face of a rapidly-declining audience. It's seriouly admirable that some of them have stuck around, but back to the "incentive" claim let's look at some facets of that:
Money? No, that's the App Catalog, the trickle-charger of income streams.
Fame? No. This is webOS; real fame potential stands only with the Big Two: iOS and Android. The most fame a developer can get on webOS is with the people that are still using webOS. Nobody pays attention to webOS releases as a harbinger of success like they do with the aforementioned platforms. Hell, when's the last time you saw a "new" webOS app promoted on a site--personal blogs excluded--other than this one?
New Blood? While it's great they're working on Preware 2 built with Enyo, I can't think of a single reason this would stand as incentive for a developer to adopt webOS as a platform to develop for. If they do develop for webOS, they're doing it for a quick buck where people often buy apps simply because it's something new in order to show support regardless of what it actually is--which means it's going to the App Catalog.
Ex-webOS Developers? For developers that have left for greener pastures, this still doesn't give them a reason to come back. If they're using Enyo, they're doing it to use the knowledge they took from developing for webOS to make money on other platforms. There's a laundry list of developers (James Harris, Inglorious Apps, Hedami, etc.) that took that knowledge and ran--largely without looking back. And developers won't be looking back until there's retail devices and some proof of success this time, either.
(Astraware, one of the last top-tier developers for webOS, hasn't even been back to the forum here--and I mean visited at all--since November of last year according to their profile, so I count them as "ex-developers" as well. This is all they've sold for the Touchpad since December, 2011, amongst a half-dozen released titles. This is why there are no top-tier developers left. Money talks.)
Current webOS Developers? The developers that are still maintaining their patches and homebrew apps for "legacy" webOS are already visible on all the same devices with the current version of Preware. This just offers them a more contextually and aesthetically-appropriate experience within the Enyo framework.
tl;dr: The App Catalog itself is already built with Enyo; this is merely a cosmetic makeover for Preware to promote the flexibility and aesthetic of Enyo, offer it to the devices that can support it, and it gives them a chance to get away from the old Mojo version once and for all. Nothing more, nothing less. Evolution, not revolution.

Despite my optimistic nature, I had to wonder if your post really made sense, and it was time to relinquish.

Then I read what your wrote - Jan 3rd of this year.


[" There's simply nothing to back up the assertion that LG was going to choose webOS when they've just invested heavily again into Google's ecosystem having just announced an entire line of televisions powered by Google TV.

According to this site, the whole reason for looking at Open webOS was to get away from Google's heavy handed terms so, well, I think we can call this site's source bunk until proven otherwise. "]

I think the wise showed up.


What goes into the feeds is not of concern until we have a working OS, being able to access them is.

Open webOS doesn't ship with Mojo, and we need a package manager. That and (in my personal opinion) Preware has been long overdue for a rewrite in a newer framework.

Also, it's worth noting that the App Catalog is written in Enyo1, whereas Preware 2.0 is written in Enyo2- there are some important differences.

I hate to break it to you but there's a new game called Tennis in the Face and they did sell quite a lot given the release was very recent.

Also, there are more new apps that sell well. Look at the new Neato for example.

OK, I'll bite...

No one who spends any time on this website has any illusions about the state of webOS. Bear in mind the Editor in Chief uses an iphone and wrote an article entitled, "Not with a bang, but a whimper".

It seems to me that there are two reasonable responses: Misery or Optimism. Misery, while understandable, gets us nowhere. Optimism might just spur some activity that moves things on positively.

I'm afraid I don't understand are those who feel the need to post lengthy 'reality' checks. To me it is like visiting an economics website to tell everybody that the economy is in bad shape and all their talking is a waste of time. WE ALL KNOW YOU'RE PROBABLY RIGHT ANYWAY.

Nonetheless, I'll try to clarify my comment:

OK, I agree: Evolution, not revolution. But an update is better than abandonware.

Current webOS Developers? Well, if they're still developing for this platform, then I tip my hat to them for having greater optimism than me. I doubt they make any real money from the platform, but if they remain willing to put out freeware to the community, at least it is well presented in Preware 2. (and see below)

Of the Ex-webOS developers: I completely understand their need to make money, but some may still look upon webOS with some nostalgia and the evolution from Mojo through to Enyo 2 maybe an easier framework to develop in, given their experience. (and see below)

New Blood? Maybe (see below)

Fame? Well on this site, YES! I won't list the 'hero' developers of homebrew because we all know their names - just read the articles from the last week. Wider fame? Maybe with a great app, but probably not.

Money? See fame, but change YES to NO and "probably not" to "how good is the app?"

Now, here is the 'below' bit:
I'm not a developer, but I understand that Enyo is easy to develop with and is a cross-platform framework. Write once, deploy everywhere. This is how it is being sold.

Preware 2 shows that you can not only build an app, but an entire app catalogue in Enyo 2. This might inspire developers to use this easy platform to develop for ALL platforms (including those that will return decent revenue for a good app). All apps developed in enyo 2 will run on webOS. I realise there are hardware/OS limitations to enyo apps, but again, something is better than nothing.

Just to clarify from my previous post: Tennis in the Face and Neato! are paid apps.

But I read your post with full interest and I agree for the most part.

I think at least it would be a good showcase for the Enyo framework. Enyo is not bound to webOS, you can use it for web apps or with native containers like Cordova. If webOS will ever come back, it is good to have developers who already know the framework. Thus I think it is good to attract new Enyo developers.

I'm willing to break my phone for this lol

Just to clarify- Preware 2.0 is not limited to installing Enyo apps. The tweet that sparked this point was in reference to Open webOS, which presently has no Mojo or PDK support.

I thought there was Mojo support since some devs found Mojo traces and a way to enable the framework in OWOS?

This update it´s only for the TouchPad!!!???

If so: The same developers are exterminating life of webOS hardware. I have a HP Pre 3 and I'd like to continue to have updates!!!!

Of course you will get updates on your Pre 3. Just because Preware is moving from Mojo to Enyo in their new version doesn't mean the servers will be made unavailable. In fact, the same server that power Preware for Pre 3 power this new version.
And maybe you can run it on the Pre 3. There are some Enyo 2 apps that run well on the Pre 3 like Top Watch for example.

It's my understanding previously... and somewhat confirmed by the article above...

"Thanks to its Enyo 2-based status, installation of Preware 2 on varying webOS hardware shouldn't be an issue. Even on older webOS smartphones, the Enyo 2 framework can be packaged with the app at a size under 25KB while still giving cross-platform compatibility and speed. For his part, Palmer's screenshots were taken on a TouchPad running webOS 3.x"

The Enyo 2 rides along with the install package as a small addition... It should deploy to/operate on a 2.x phone.

If I'm incorrect it is due to a layman's mistaken impression and a more tech savvy type will correct me. :)

In addition to the replies above - if you look closely at the screenshot in Derek's follow-up article [*] you'll see that PreWare 2 Alpha runs on webOS 1.3.5 and above (assuming the info in the picture is correct).

[*] http://www.webosnation.com/preware-enyo-alpha-hits-preware-feeds

Preware-Alpha in the alpha app testing feed is this enyo2 based preware. to be clear: It works on ALL LEGACY DEVICES in addition to OpenwebOS. Keep in mind it is an alpha and all of the alpha warnings apply.

In terms of legacy webos it installs anything, mojo, enyo, pdk, hybrid, etc.

In terms of openwebos it will only install enyo based apps at this time as mojo was not opensourced and will not be opensourced. PDK apps are not currently working on openwebos either.