Mojo is an MVC (Model-View-Controller) application framework, based on the HTML 5, CSS, and JavaScript web standards. Applications that are built using Mojo can be run at native speeds and have access to a wide range of APIs to access device specific functions and services.

Hearing anything familiar to the iPhone’s development stature during it’s first year?

We’ll you shouldn’t.

It’s a completely different situation.
Apple was forcing users to create iPhone optimised web applications.
In order to do this, the end user had to open Safari, and navigate to the web application. Something that was improved in a later release with icon short cuts on the main screen, but still unable to match the look or feel of any of the native Apple applications.

In contrast to this, Palm use their own SDK (JavaScript and HTML5) for all of their own applications. It’s integrated and consistent across all applications, with a specific bespoke API for interacting with the device or doing webOS specific functions.

The Mojo SDK contains a number of useful pre built widgets you can use, such as buttons, checkboxes, date picker, drawer, filterfield, list, people picker, progress bar, rich text edit, and a webview.
As well as a number of useful utility classes.
The whole Mojo framework is unit tested using its own bespoke unit test implementation.

Using the leaked SDK on an Apple Mac, I’ll be putting together a quick hello world tutorial for those getting started.

Firstly you’ll need to download and install Virtualbox.

It’s a free virtualisation software for x86 hardware created by Sun. It is used as an emulator by the SDK by loading the webOS image.

Secondarily you’ll need to download, and install, the SDK.

MAC, Rapidshare
WIN, Rapidshare

It was leaked by someone else, not myself, so I’ll link to their SDKs.

Now that you have everything installed, I would recommend having a play around the phone, and getting a feel for the interface and the conventions of the pre built applications.
If you haven’t had a chance to play with the actual device yet, you can definitely get a feel for how it behaves.

Palm Pre

In order to create our application, we need to generate a base to build upon. The base that you’ll be generating provides you with a folder structure, and application information files.

1. Open Terminal.
2. Enter the command "palm-generate HelloWorld" and press enter.
3. You’ll receieve a message stating "Generating new_app in /Users/{username}/HelloWorld".

Open the /Users/{username}/HelloWorld folder in Finder. Replacing the {username} token with your username.

Within the HelloWorld folder you should see the following;

app (folder)
JavaScript class files

appinfo.json
used to specify a unique name, version, and icon information

icon.png
icon for the dashboard

images
PNG/JPG

index.html
the default view

sources.json
Seems to be used to list all of the files used by the application for the packaging process?

stylesheets
CSS

Editing the appinfo.json file allows us to add a unique name, and change the vendor, so we’ll do that first.

Opening the file will display the following:

{
	"id": "com.yourdomain.helloworld",
	"version": "1.0",
	"vendor": "My Company",
	"type": "web",
	"main": "index.html",
	"title": "HelloWorld",
	"icon": "icon.png"
}

The file format is a JSON (JavaScript Object Notation) file, basically, a readable format representing associative arrays, objects, and simple data structures.

The values are in the following format "key":"value".

Lets start by altering the unique id of our application, so change the value of "id" from "com.yourdomain.helloworld" to "com.test.helloworld".

Alter the other values to match the appinfo.json file below.

{
	"id": "com.test.helloworld",
	"version": "0.1",
	"vendor": "TestEvaluationCompany",
	"type": "web",
	"main": "index.html",
	"title": "Testing Hello World",
	"icon": "icon.png"
}

There are more potential key-value pairs we could add to the appinfo.json file, below is a list of the ones I know of so far. Please do let me know of any more you find via the comments.

id
Unique identifier for your application.
Recommended usage is to use a reverse DNS notation (com.domain.appname) in lower case characters.

version
Versioning of your application in a Major.Minor format.
Best to keep to this format as it could be used for over the air downloads/updates.

vendor
Company or individual who created the application.

type
Application type, which should be “web”.
This seems to be a clever way of future proofing there install process, potentially “native”, “java”, or even “python”?

main
Initial HTML file to be displayed when the application is launched.

title
Displayed in the launcher, and in the top grey tab, which I wish to affectionately call, the tabular.

icon
Path to the icon used for the launcher screen.

vendorurl
URL of the company or individual.

miniicon
Path to the icon used for the notifications.

Now we’ve gone far enough to test our application. It will show up as an individual application on our home screen, but not do anything other than display a predefined message.

But it’ll be good to test and get someone up and running now, so lets go.

First of all you need to package your application into a IPX file.

An IPX file (or an Itsy Package) is an installable package apart of a lightweight package management system designed for embedded devices, similar to Debian’s dpkg.

Packaging is done via Terminal;

1. Open Terminal.
2. Enter the command "palm-package ~/HelloWorld" and press enter.
3. You’ll receieve a message stating "Creating package in /Users/{username}/com.test.helloworld_0.1_all.ipk".

Now we have the package, we could send it off to a friend to test, or presumably, off to Palm to enter into the App Catalog.

Installing an application on the emulator;

1. Open Terminal.
2. Enter the command "palm-install com.test.helloworld_0.1_all.ipk" and press enter.
3. You’ll receieve a message stating
   "connecting to device emulator (###)
copying /Users/{username}/com.test.helloworld_0.1_all.ipk to /media/internal/developer/com.test.helloworld_0.1_all.ipk on device emulator (###)installing package /media/internal/developer/com.test.helloworld_0.1_all.ipk on device emulator (###)".

You’ll now be able to click on the launcher icon and see your application. The icon is the standard unchanged ‘blue square with crescent moon’, with the label “Testing Hello World”, as we specified in our appinfo.json file.

That’s it for our introduction. In part 2 we’ll start to create a real world application.

These days, Palm are getting their swagger on. With a brand new device, why shouldn’t they feel more confident?
Shipping over 100,000 of their flagship Palm Pre devices, with another 100,000 in July and 200,000 estimated to ship in August. Completely destroying Sprint’s current sales record in the process.

Not content with re-entering the race with a brand new device, and first mainstream mobile phone wireless charger, the Touchstone, they have also developed a new operating system, the webOS.
webOS uses Synergy to sync with Facebook, Google, and numerous other vendors to provide one central location for your contacts, settings, emails, events, memos, tasks, and software downloaded from the App Catalogue – all happening over the air, everyday, without disturbing your focus.
Not only does this remove the one, single, authoritative, central repository of information, such as your home computer, it also removes the liability factor of losing your device and losing data at the same time. All data is stored on cloud-based services that feed the device contextual information, and data. This is a break from the current functionality of the iPhone, and other smart phones, but it’s a definite advantage, and one sure to be adopted by the next generation of devices.

iPhone, Pre, N97/N85; are we beginning to see an era of powerful connected consumers?
We think so, we predict, and we are on the forefront of enabling consumers to stay connected.
In terms of statistics, 735,000 users accessed Twitter via a mobile device, and YouTube mobile uploads have increase 400% a day since the release of the iPhone 3GS.

Users are starting to get comfortable with this kind of access, and they’ll begin to demand more of a connected computer experience. Mobile phones are no longer phones, they are bordering on becoming mobile internet devices (MID, as pitched by Intel).
What’s stopping these consumers from becoming the connected consumers of the future? A few different aspects, but vendors are starting to make inroads to battle these obstacles.
Adobe’s open screen project is starting to bare fruit, with the release of the Flash Player 10 for Google Android, and the commitment to release the runtime for the Palm Pre shortly.
What does this bring for consumers? Well, the real internet.
Without Flash, a magnitude of web sites are rendered inaccessible, but also many rich internet applications. Opera’s MAMA studies (from Oct 08), have found that 32% of websites use Flash in the United States, and 30% in Great Britain – even at it’s worst, it never dips below 25%.
The same can be said about Silverlight, as well as HTML5.

With potential cross platform runtimes, such as Flash, Silverlight, and even browsers (HTML5), vendors can start producing applications, and platforms to do a magnitude of functions.
Anything from GTD (getting things done) to location based services and applications have started to appear, storing data in the cloud, while allowing persistent data to be cached or stored locally in databases, and shared objects.
While the industry hasn’t yet begun to explore what is possible with Augmented Reality and location based services, at least some progress has been made, with very, very, very, very impressive applications being released for multiple platforms.
In contrast to the VOD (video on demand) industry, where players such as the BBC’s own iPlayer has made inroads on the iPhone, N85/5800/N96, and the HTC Touch HD, we have yet to see the VOD niche to take off.

Primarily this is due to the VOD services still being in their infancy, but soon we will start to see better support for H.264, in the form of graphics, and video decoding chips embedded within the devices (Tegra), or via software ala the rich runtimes (Flash/Silverlight).
With nothing holding the industry back, the potential for  VOD services and platforms to take off and innovate will be similar to the effect that 3G had for mobile devices back in 2003 (when it went mainstream with Three).
And this is where we come out with our predictions, 2010, video on demand and semantic advertising to assist in generating a solid return on investment for vendors.
Larger screens, location aware adverts (E.g, giving you directions to the nearest store),  high definition, locally stored cache, and QR codes within adverts/posters for series/brands.
Unfortunately VOD services are being branded, and pushed, as catch-up services. Starting to push them as a medium on their own will propel them into the mainstream, allowing connected consumers to watch what they want, when they want.

Utilising the standardised technologies prevalent within the existing video on demand industry, such as Flash and JavaScript, the Palm Pre has an obvious advantage.
Rich interfaces, a common code base and a huge base of developers that are familiar or easy to transition too.

Hearing anything familiar as the arguments behind the iPhone’s development stature during it’s first year?
We’ll you shouldn’t. It’s a completely different situation, Apple was forcing users to create iPhone optimised web applications. In order to do this, the end user had to open Safari, and navigate to the web application. Something that was improved in a later release with icon short cuts on the main screen, but still unable to match the look or feel of any of the native Apple applications.
In contrast to this, Palm use their own SDK (JavaScript and HTML5) for all of their own applications. It’s integrated and consistent across all applications, with a specific bespoke API for interacting with the device or doing webOS specific functions.

Anything created for the Pre would be completely HTML5 compliant, and this not only reduces the amount of bespoke (potentially redundant) code, it also allows vendors to explore the future.
With Firefox 3.5, Opera 9.5, Chrome 3 and Safari 4 supporting the video, and audio playback portion of HTML5, how long until vendors can justify using bespoke implementations for each devices, when there is the potential of using HTML5, or Flash to create their platforms. Cloud computing, standardised technologies, and rich interfaces are propelling the mobile devices into a new field, with new possibilities.