Deliver your J-Mango script via QR codes

I am really excited! Duc just managed to put together a new J-Mango runtime that includes the ability to load j-mango bytecode from a 2D bar code (Datamatrix and QR). Check out this video to see what I mean.

Currently every QR code implementation we have seen requires jumping to the URL. Well, now you can embed your whole workflow into an offline QR code (within limits).

The functionality is currently user initiated (”read from photo” via the j-mango menu). Next step is looking at how we can integrate script commands so developers can load data/script segments etc from within script.

The code is currently in our labs, until we are sure it is solid - but feel free to leave some feedback on where this could go. Better still we would love you to be a tester for our upcoming beta.

Mob4Hire: Mobile Testing made easier crowsourcing style

Just saw this post for a crowdsourced mobile application testing community.

Its an interesting idea. We had an idea for something similar when we started j-mango because the costs involved in maintaining an inventory of phones to do testing with keeps on rising (we have lots of phones to give away if you want one!).

Since then we have found Device Anywhere which is an amazing paid service that mimics phone’s and network conditions - you still have to schedule time on the phone though. There is also the free Nokia Remote Device Access however it is limited in terms of the devices you can test - there seems to emphasis on S60 based devices which are but a limited part of the of the Nokia not to mention the overall mobile landscape.

While DA and NRDA make devices and network availability a mute point, as I mentioned in a previous post, the sheer variety of phones and configurations means that you are simply limited by how time you have to do the testing. I think Mob4Hire addresses that need by spreading that testing load.

I’ll be giving Mob4Hire a try and posting some updates.

Coffee ordering on your phone: J-Mango’s first client goes on live trial

Coffee lovers who hate waiting in line to get their morning fix can now place orders and have it ready by the time they reach the store.

One of j-mango’s first clients, Cosmo21, are running a live trial at Michel’s Patisserie at Melbourne Central (in Melbourne, Australia for the international readers).

Cosmos21 has used J-mango to build a coffee order app that works on your mobile phone and integrated it into their very popular POS systems which they supply to some of the largest coffee chains in Australia.

Its even got a cute red beacon to alert the store owner when the an order comes in from a mobile.

Cosmos21 is bringing this idea to market under the name of “Solutions 2 Go”

I’ll post more details and some juicy photos as they become available.

Links:
Cosmos 21
Solutions 2 Go
Pos 2 Go

What is J-Mango? You tell us.

I get asked all the time to explain J-Mango and I still struggle.

This isn’t a recent problem. Since it’s inception, we have been trying to articulate simply what j-mango is. I am happy to report we haven’t been successful - because as was recently pointed out to me, it could be because it’s a totally different kind of animal.

And that’s a good thing.

I can tell you why we came up with j-mango:

1. The user experience on the mobile web sucks: Telco’s in their quest to drive usage of data have been delivering more and more bandwidth to the device. Unfortunately this is like asking someone who is thirsty to drink from the mouth of a firehose. The render time on most devices takes a long time.Worst still, a mobile phone user who uses his mobile phone for purely voice and SMS now has to navigate a rich web on 240×320 screen (if lucky) with no keyboard and no training?!
2. The mobile development experience is terrible: The complexity involved in developing something for a mobile app is mindblowing. You have to worry about
   • The various phone models with their imperfect J2ME implementations
   • Telco network lock downs and custom configurations of their handset
   • The upgrade cycle should you decide to change your app

Quite simply, for a web developer used to scripting with their tight ‘code N reload’ style of development methodology - The mobile development experience is like going back to the assembler days.

But here is the sad thing… most web sites could benefit from a simple mobile component that would tremendously increase the stickiness of the site. Case in point - dopplr, docoloco.com, yelp.com, geezeo.com, wasabi.com etc.

If only the bar was lower, if only you didn’t have to understand “mobile development” to get something on the mobile…hence we built j-mango. Check this video out to see what I mean.

We are working on getting to launch. If you are for a simple elegant user experience on the mobile and If you are for a simpler way to develop mobile extensions to your cool web apps. Help us.

We are looking for a simple explanation/tagline of what j-mango is/does/improves. . If you have ideas let us know by visiting http://www.j-mango.com

The complicated mobile web

Just came across this article on “Coding for the mobile web”. Wow! And you thought IE vs Firefox compatibility was a problem!

25-Apr-2008! Hello world J-mango!

Wow. J-Mango is finally free. We can now start doing things the way we always wanted to! Expect more posts.