Ok, well it isn’t finished yet (not even at beta!) but I thought I’d share some screen grabs from both Android and iOS. We’re making rapid progress…
We’re obviously stripping the functionality right back for the mobile app; focussing on simple, every day tasks:
Beta, Releases & Timing
We have no firm dates for release… yet! But by the end of May we should be in the position to make mobile Contacts and Calendars available as an unsupported public beta; by June I would like to see Timesheets and To-Dos added to the beta.
We’ll be initially running a “at your own risk”, unsupported public beta; requiring any issues to be posted to a forum.
This is because we’ll be rapidly developing, simultaneously as we release-to-beta so we’re likely to catch and fix any bugs by the time we address individual support issues. It would be a horrible waste of development time to be addressing issues individually, after they have already been solved (even to update). So – unsupported public beta it is.
Mobile CSS, then Android & iPhone natives
Our development path on this project is to quickly deliver something that works on all mobiles and then to double back, package up and release native/hybrid Android and iPhone apps.
The mobile CSS version would be 100% functional on all web enabled mobile devices, the only difference being pretty formatting. On Android and iPhones, the formatting will be optimised already.
Then once we’re through a beta period and everyone is smiling, we’ll package up Android and iOS versions and push through as native applications.
All mobile versions will be a free, zero cost, add on to all existing customers who have signed up before we take the mobile version out of beta. This remains true to my ideal of rewarding customers who stay with WORK[etc], help us work through the niggles and build a truly world class product.
For all new customers after the release, it will be a small additional add-on to the monthly subscription.
I really hate this phrase, but continuing on from my recent blog post, it occurs to me that yet again we’re using our product to build our product. The mobile app will actually be built 100% on top of our own API; that is the same API customers use to build custom integration into their software. I thought this was pretty cool.