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
Occasionally while developing, you get the urge to add a little personal flavor in your application. Let’s spice up one of the more under-appreciated widgets on the platform: the spinner. Since we should be providing the user some visual feedback while waiting on a response from a service/device, many apps make use of the spinner widget
The webOS 2.1 SDK has officially exited the Early Access program and is now available for download from the HP webOS Developer Center. Using the 2.1 SDK, you can now: Take advantage of unique webOS features like Just Type, Exhibition and Synergy. Build and distribute hybrid apps, combining HTML, JavaScript and CSS with C/C++.
After announcing the next exciting chapter of webOS at February 9’s Think Beyond event, we took our show on-the-road, hosting a webOS App Developer Conference at Mobile World Congress.
As we make the transition to Enyo, developers can still take advantage of Mojo, especially with the upcoming releases of the HP Veer and Pre 3. And while you’re probably very familiar with Mojo, perhaps you aren’t aware of how you can take advantage of the many existing JavaScript libraries that work seamlessly with Mojo
This has been quite a week, with the announcement of an incredible lineup of devices in the Veer, Pre 3 and the TouchPad and a closer look at the next generation of webOS development with our new Enyo framework. Now, I’m sure many of you are wondering where that leaves apps you’ve developed or want to develop with Mojo
Development frameworks don’t make for exciting gadget news, but HP’s Enyo is kind of a big deal. It’s the little dealie that allows new webOS apps to stretch between vastly disparate screen resolutions — say, tablet and phone — and still work just fine, and since it’s based completely on web technologies, they can also run in a PC browser with no formal emulator or OS install required. While dev team lead Matthew McNulty pitched the browser functionality as a debugging boon, we’re starting to wonder if that’s how HP could bring webOS to PCs to start — rather than a dual-boot or a UI layer, it could simply make your favorite apps available in a web store
When developing and pushing the limits of webOS applications, it can be helpful to know some of the boundaries you might run into. Here are a few that have come up in the past for other developers: Maximum size for an ipk file (i.e., the app package): 200MB. You can locally install larger ipks, and you can also grow your application resources after installation by downloading or dynamically creating additional content, but this is the biggest ipk file that can be uploaded to our catalog server.
The Google Web Toolkit™ software development framework, or GWT, is a great open source SDK that lets you build web applications using the Oracle® Java™ language.
T-mobile G2 now $50 cheaper on RadioShack Android Development Talk (blog) … of attraction for many upcoming devices to boost their sale as well as devices that have lost their presence in market be it the G2 or the Palm Pre . …
Setting up PhoneGap to work with Xcode® In this tutorial, we will take the Stars app developed in Part One for webOS™, and in Part Two for Android™, and port it to iOS™ using PhoneGap as well. To start with, if you’re going to use PhoneGap to create iOS apps, you will need a Mac running Apple’s MacOS X, and have their Xcode® toolset and iOS SDK installed.
PhoneGap with Android In part 1 of this series we built a simple Canvas based app that ran on webOS using PhoneGap rather than Mojo. Since PhoneGap is designed to support multiple platforms we can now port our app to another OS with very little work
