There goes Google, taking it to the next level again. Their latest offering is Google Local for Mobile. What they’ve done is essentially taken the Ajax model for desktop browsers and brought it the phone using J2ME. The idea is to have a fairly lightweight MIDlet (38k for the MIDP2 version) that then grabs all the data neccesary from the network.
While this isn’t a horribly new idea, I think in this case it’s all about execution. Check out the tour to see everything that they’ve crammed in to this midlet. Your basic search is there, directions are there, simple smooth navigation is there. The interface is clean but at the same time there is a ton of information at your fingertips. They’ve also managed to cram driving directions in there, which is something I miss from MGMaps. To be fair, MGMaps has had a j2me interface to Google Maps for quite some time now and it’s the most used MIDlet on my phone. More than once it has helped me figure out where I am or where I’m trying to go.
I’m glad to see Google pushing the mobile space like this. At the same time with mobile devices and J2ME you’re going to run in to some glitches. For example, I snagged the JAD by going to google.com/glm with Opera on my phone. It snagged the JAD and started installing it. After downloading it promptly ran out of memory and quit the installer. This isn’t Google’s fault, it’s the 6682’s known lack of a decent amount of memory. What worries me is that if the installation process failed on a rather high end device, I worry about how it would do on a super generic low end flippy. What is even worse is that after downloading and bluetoothing the JAR to my phone, I don’t get any farther than a bunch of “Loading…” on my screen. It looks pretty and fun in the emulator though.
While there are still some growing pains to get through, Google is definitely on to something. To get around the problem of mobile browsers sucking, why not just get rid of the browser completely?
Update: Thanks for the comments everyone. On Niels‘ suggestion I tried Other -> Nokia -> 6682 and it worked like a charm. Someone needs to fix the Cingular -> Nokia -> 6682 JAD.