blog : OHAdev.com


Dalvik

Updated 11/13 12:12pm, see bottom of article.

It’s now been over twelve hours since the Android SDK and documentation hit the web. Before I sleep, here is a rundown of one of the technical aspects of the Android release that surprised and impressed me the most. By far the biggest, ballsiest move we saw from Google today was the announcement of the Dalvik Virtual Machine within the Android architecture. Following the Open Handset Alliance’s initial announcement last week that revealed Android would be using the commercial-friendly Apache v2 license for everything but its linux kernel (here’s a good Ars Technica article explaining why), there was much speculation on what sort of development environment Android would adopt, since Sun’s own open-source reference implementation of J2ME (phoneME) is GPLv2 and therefore incompatible, and Sun was conspicuously absent from the OHA lineup (despite the CEO’s public approval of the project while promoting the Netbeans IDE).

Sooo, what about Google Android and phoneME?

Read more

OHAdev’s own Greg: post on ZDNet communityOHAdev’s own Greg had the featured story on ZDNet Community today (SDK day), discussing the role of developers and community in the success of Android with his post “Why you should care about Google Android“.

From Greg’s posting:

[…] With an open standard such as Android to build upon, Google’s mobile initiative is much more likely to survive than if it had gone with a more “standard” approach to entering the phone industry (a la the iPhone).

With a strong community of developers, Android could forge new, unexpected collaborations between programmers, allowing them to iteratively increase the platform’s stability and utility to your average mobile handset maker or service provider.

No, this doesn’t mean that your average student programmer will be able to make the next iTunes–it has always been the case that good, beautiful software still takes lots of design, hard work, and testing, but what we may see with Android is a slight twisting of the nozzle, pressurized by the force open-source software, starting to empty into the giant, empty pool that is the mobile phone market.

Stay tuned for our end of SDK-day wrapup, we’ll be helping you digest the massive SDK release and offer our thoughts on what it will mean for mobile development.

OHAdev on an Android Phone?

Posted by Brian at 17:04 | Filed In blog, emulator | 1 Comment

OHAdev through the Android emulator

Not quite, but you can get to us through the emulator!

We’ll be performing a more thorough analysis of the Android emulator applications and the ~2000 SDK classes later today.

Android Emulator load screenWe’re still digging through the Android SDK’s overwhelming documentation, but I thought I’d share with you some initial impressions about the emulator and code samples. Because Android-compatible hardware isn’t scheduled to hit the market until the second half of 2008, the Android SDK includes an emulator that mimics the environment of a mobile phone on a standard PC desktop - a standard practice for any full-featured cellphone SDK. Just run the file “emulator.exe” in the “\tools” directory after unzipping the SDK, and you’re good to go. From here, you can play around with the Android default GUI and application suite as seen in the official Android demo video, which includes a web browser, maps, phonebook, etc.

If you want to try out the API code samples and game demos, you’ll have to set up your development environment, which isn’t too difficult if you have used a Java IDE previously. Follow the instructions here to integrate the emulator with the Eclipse IDE, create a new Android project with source from one of the projects in the “\Samples” directory, and you’re good to go. Read more

… patiently waiting for SDK

Posted by Brian at 09:19 | Filed In blog | Add a Comment

Baby wants his SDKIf you’re as excited about the SDK’s launch today as we are, you may be wondering how the Open Handset Alliance defines “November 12, 2007″.

Unfortunately, it appears they do not define it as 12:01AM EST, November 12, 2007.

The forums are bumpin!

I currently work as a game developer at Javaground, a mobile phone game company based in Southern California. My coworkers and I are all well aware of Google’s Android announcement, and I’m sure everyone in the mobile game industry is waiting with baited breath to get their hands on the “early look at the Android™ SDK” announced to be released into the wild tomorrow, November 12. With a very ambitious press release and such a huge consortium of industry players (and with the industry giants notably absent from the Alliance), all of us game developer types are all wondering one thing: What could Android possibly do for mobile gaming?

Read more