ubikapps.net

Mobile Development Blog

Entries Tagged ‘g1’

Benchmarking Protobuf vs JSON parsing in Android

I have a bit of an addiction to benchmarking. It must be because I’m a PC gamer (yes we still exist). Actually it’s probably more of an addiction to tweaking every last ounce of performance out of something. Recently I learned how to get to the protocol buffers version of the Google Reader API. Protocol [...]

On Android Fragmentation

During development of the SMS Bot Widget I encountered some issues with running it on the different versions of Android. The SMS API changed in Android 1.6 and the contacts one changed in Android 2.0. Coding for 1.6 and then attempting to run it on 2.1 meant that some nasty bugs cropped up such as [...]

Benchmarking JSON vs XML Parsing in Android revisited

In my previous post on this I mentioned that parsing the Google Reader XML (Atom) feed with SAX was faster than parsing the JSON stream with json-simple. However, this is no longer the case thanks to jackson which is used in the Reader Widgets from version 2.3. On my HTC G1 running Android 1.6 (donut) [...]

Dear Santa…

… I’m not asking for anything for this Christmas but for next year I want the perfect Android phone to be released. Maybe a keyboardless Droid, maybe the Nexus One, Two or Three (or six?) but with the following: 3.7 inch 854×480 screen Decent camera with: Flash (xenon if possible) Physical button that can be [...]

Senseless Sense

Don’t get me wrong I love my HTC Hero and it’s Sense UI. I just don’t like the fact I have to wait longer for Android updates compared to other phones. I’m sure when Eclair comes to the Hero it will be great but I just can’t stand missing out on all the new apps [...]

Reader Widgets and Android 1.6

I have installed the official Android 1.6 (aka Donut) ADP build on my G1. I’ve done some initial testing and found that both Reader Widget Small and Reader Widget Pro work on it. I have also uploaded screen shots for both to the market (only visible in the 1.6 version of the market). PubCrawler still [...]