[brown9-2]

Would you guys care to elaborate on some point in the future just what it was about the Android platform that let to your app being the "buggiest" on it of the three?

Your experience might contain some good tips or lessons learned for other Android developers.

[jlgosse]

I disagree with Greg 100% on that statement. It has been a real pain working with the Android bluetooth APIs, but the same can be said for the BlackBerry APIs as well. They work great for something that is persistently connected, but since we don't actually stay connected all night, managing the bluetooth connection can get messy very quickly.

In my experience (since I developed the entire BlackBerry app, and did a lot of work on making the Android app a lot more stable than it was), the apps are working great right now, and they get better every day or two. I mean, I push updates to the app VERY often, and our users have no problems with it, besides the occasional bug, which I generally fix in the following hours.

My only real comment on the matter is that writing code that works well with Bluetooth is REALLY hard, so if you can keep a persistent connection when the app is open, try to go that route.

[brown9-2]

I can't tell if he is stating that Android was the buggiest of the platforms that Wakemate is available on, or if the Wakemate app on Android happened to (initially) turn out to be the buggiest of the various Wakemate apps on the various platforms.

[jlgosse]

Now that you mention it, I don't know either. As a whole, I'm sure the Android platform is buggier, especially in devices with an OS less than 2.1, but overall I think BlackBerry the OS is buggier.

One big problem with Android though, is that some of the phone manufacturers decided that it was a good idea to tamper with the standard Android Bluetooth code, so that caused (and still causes) some seriously problems.