About Android
I receive several emails and messages every day asking me the same thing: “Are you making an Android port? When is it going to be ready?”.
I don’t hate Android. I know there are a lot of people who would like to have PipClock on their Android phones.
I really, really want - as I said few months ago - to port PipClock to Android.
But unfortunately, right now, I’m unable to create an Android version for several reason.
The SDK I’m using, Corona SDK, can export natively to iPhone and Android. Problem is, while almost every API command support both platforms, some elements are not yet supported on Android.
The MapView element, the one you see below the Geiger Counter, as well as a hidden one to manage all the GPS positioning, manual location, geocoding and so on, is NOT currently supported on Android platform.
Besides MapView, there are other commands not working on Android, especially for the new functions coming in PipClock 1.3.
Long story short, I’m stuck until Corona SDK fix those problems and add Android support for the API I’m using.
Developing an Android version cutting the unsupported API (therefore missing some features compared to the iPhone version) would result in an entire, independent, code branch. That means, every time I add a new feature, every bug I fix or part of code I change, needs to be adapted to two different branches of code.
Maintaining two independent branches of code it’s unfortunately something I can’t currently do, since I don’t have the time/resources…
Keep in mind that behind PipClock, behind every line of code, every pixel, every sound effect, every message on Facebook, every support email, there’s just one single person: me.
Keep also in mind that while I’m very happy how PipClock is so well received (great reviews and user feedbacks), is not exactly a super commercial success, let’s say it’s more comparable to a part-time job… That’s why I still need a full-time job, and dedicate my spare time and nights working on apps.
So, are you planning an Android version?
Hell Yes, I want to port PipClock on Android!
When is the Android version going to be ready?
Basically, when I’ll be able to maintain a single branch of code for both platforms. That means, as soon as those API I need are supported on Android.
It’s definitely on Corona SDK Roadmap. There’s a major update of the SDK coming in the first days of August.
I’m not sure, but I HOPE the new update is going to fix those problems.
In that case, I’ll definitely continue working on the Android port.
By the way, since Corona SDK supports natively Android, as soon as I’ll be able to use the API I need on Android, the porting is going to be very easy and fast. I estimate probably 2 weeks.
About PipClock 1.3
It’s coming and is going to be great, but is going to require some time.
I’m currently working on a new app (going to be released soon, and I bet you’re going to love it) using many technologies I developed for PipClock 1.3… as soon as that app will be released I’ll shortly release the new PipClock major update.
(the communication modules is coming… as well as many other “nuclear survival modules” in the near future!)

