Google Android - The Android Log
Gizmodo reader shows Android in the wild
January 1st, 2008 by Head RobotFrom Gizmodo,
Our source, a Giz reader, had some feedback to add to the prototype, which he used for a day: Even in early form, it’s light and fast, much faster than the desktop emulator at times. And as a longtime programmer, he thinks it’s a lot more put together than Window Mobile 5 on the back side of things.
Read the rest of the story at, Gizmodo reader shows Android in the wild.
Technorati Tags: mobile phone java application, java applications for mobile, mobile phone java apps, mobile phone application, java for mobile phones
Android Developers Blog - Example Application, A stitch in Time
November 22nd, 2007 by Head RobotPosted by Dick Wall, Google Developer Programs, on the Android Developers Blog
Background: While developing my first useful (though small) application for Android, which was a port of an existing utility I use when podcasting, I needed a way of updating a clock displayed on the UI at regular intervals, but in a lightweight and CPU efficient way.
Problem: In the original application I used java.util.Timer to update the clock, but that class is not such a good choice on Android. Using a Timer introduces a new thread into the application for a relatively minor reason. Thinking in terms of mobile applications often means re-considering choices that you might make differently for a desktop application with relatively richer resources at its disposal. We would like to find a more efficient way of updating that clock.
The Application: The rest of the story of porting the application will be detailed in future blog entries, but if you are interested in the application in question and the construction of it, you can read about it in a not-so-recent Developer.com article about using Matisse (a GUI builder for Swing). The original application is a Java Swing and SE application. It is like a stopwatch with a lap timer that we use when recording podcasts; when you start the recording, you start the stopwatch. Then for every mistake that someone makes, you hit the flub button. At the end you can save out the bookmarked mistakes which can be loaded into the wonderful Audacity audio editor as a labels track. You can then see where all of the mistakes are in the recording and edit them out.
Learn how the application was built and grab the source code at, Android Developers Blog: A Stitch in Time
Technorati Tags: Android, Application, Google, SDK, example, source-code