When HP announced last month that it would open-source webOS, the outfit seemed mighty pleased (and relieved) to have finally made a definitive decision regarding the fate of its $1.2 billion software experiment.
Thanks to all of you who made “Got Game?” our best App Hack yet. We had a ton of entries, which made judging a challenge, but also a blast! We saw imaginative designs and control concepts, some great kids apps, and a few nicely rendered game clones. The winner, by a whisker, is… Color Tangle by Will Hankinson Just what you wanted—another puzzle game to steal hours out of your life, right
Intel is combining its netbook and tablets, ultra-mobility, mobile communications and mobile wireless divisions into a “Mobile and Communications” super-unit. It’s aiming to catch up with the portable chip big boys like Qualcomm and NVIDIA
Editor’s note: This week we are featuring a guest challenge from rockstar webOS developer Doug Reeder. He has pioneered an app interface that he calls Desk Accessories. Your challenge this week is to create an app that uses this kind of interface
The Law Office of John J. Sheehan’s newly launched website has won the 2011 WebAward from the Web Marketing Association for Outstanding Achievement in Web Development (PRWeb October 25, 2011) Read the full story at http://www.prweb.com/releases/2011/10/prweb8895855.htm
Have you been wanting to add maps, complete with pushpins and infoboxes to your Enyo-based app? We’ve added a tutorial from our own Markus Leutwyler (@twtomcat for those following him on Twitter) that shows you all the details. You’ll find the article on the HP webOS Developer Center here
In this article, I want to share how you can help ensure that your custom kind’s components are contained where you want them to be. Let’s start with the following example: Here is a kind that is simply a VFlexBox with a Header (for a header), a Scroller (for holding whatever gets added later), and a Toolbar (for a footer): enyo.kind({ name: “MyKind”, kind: enyo.VFlexBox, components: [ {name: "header", kind: enyo.Header, content: "Header"}, {name: "scroller", kind: enyo.Scroller, flex: 1}, {name: "footer", kind: enyo.Toolbar} ], create: function() { this.inherited(arguments); } });
Around the webOS Developer Relations team, we often like to say that the developer is our customer. It drives what we do and constantly pushes us to keep asking, how can we improve the experience for every developer on our platform?
When we announced the addition of in-app purchase to webOS 3.0 , we gave developers a new avenue for monetizing apps, as well as providing more compelling experiences for users.
“Meet the Team” is a series to help you get to know your webOS Developer Relations team. It’s a friendly and fun behind-the-scenes look at the people whose main mission is to serve and champion webOS developers everywhere.
We recently introduced in-app purchases for webOS 3.0 , giving developers an easy way to provide premium content to customers and new ways to monetize their apps. In the first phase of our rollout, developers have been able to start creating and managing in-app purchase items, including item types, language settings and pricing. For developers that have been busily creating in-app items – and adding a whole new dimension to their apps in the process – we’ve got great news.
With the upcoming release of the Pre 3 and TouchPad, we will have two new webOS devices that offer different screen sizes and resolutions than we’ve had before. While these devices will be able to scale & display current apps correctly, developers who want to take advantage of the additional screen real estate will still need to update their apps accordingly
As you know, the webOS 3.0 SDK is now available to developers in Early Access . But here are a few things developers with existing webOS apps can keep in mind to optimize their 2.x-based apps, particularly around building background services
