So, now that we got the persistance across sessions and meeting restart functions approved and on the app store, it’s time to really focus on Twitter integration. We are glad we hadn’t gotten to far before this time, since Twitter has officially shut down all apps that are using simple integrations. So now we have to focus on getting a much better understanding of how the OAuth features work for twitter. In the mean time we want your feedback on how Twitter integration should work. There are a few choices that come to mind:
1) Tweet when ever a meeting has reached quorum and when it is ended, as long as you have selected that you wish to tweet. While this would be the simplest, it may not be prudent to tweet that you just wasted a ton of money by being in a meeting with your boss.
2) Only tweet when a meeting has completed.
3) Only tweet when quorum is reached.
4) Ask at each major point, do you want to tweet about this event, i.e. If you press quorum achieved, ask if you wish to tweet, or if your meetin ended, instead of asking “Was it worth it”, ask do you want to tweet, and if you answer yes, then ask was it worth it. This would allow the tweet to say “We just spent $1billion and it was worth it :)”
We think we are only a couple of days away from submitting the next version to Apple for the App Store. Data storage and retrieval between running session is within sight. Trying to decide if we should wait for twitter integration or submit this version first.
We are currently looking at Android for a version of WastedTime…Today when you purchase the iPhone app, you get a fully functioning iPad app two, not some cheap pixel doubling app. Given this, you may find yourself, like I do, having to chose between the iPhone and the iPad version for all your meetings during a week. This is because the current version of WastedTime stores it’s persistent data in the iOS’s NSUserDefaults. Meaning that it is not shared across devices.
Do you think that it would make more sense to have a data store in the cloud which would automatically sync up when you start the app? We do want to add a mashup of wasted time around the globe, but did not want to store any specific data. If we have data persistence across devices, you could show total global wasted time within the app itself. What do you think of this idea?
So, we continued to have slow and steady sales so far. It’s pretty cool to see where our next sale is coming in from each day. In the mean time, we are working on more improvements to create version 1.2. These include:
Disallowing the paste feature – some of our users have been playing with entering text in the rate field. The good news is that the program will treat this as a value of 0.
Better graphics – Our goal is to make the entire application language neutral.
Localization of the currency value – Right now the rate is currency neutral, but wouldn’t you like to see your phone’s currency setting?
Odometers instead of text – We’d like to have a spinning odometer showing you the values as they spin up higher and higher.
While each of these seem pretty easy, we will not publish until we have at least the bottom two done (they are the harder ones). We value your feedback, so drop us an email at support or comment on this post.
Well, we realized we created the category and then put all our news on the main news feed. So here it is, we officially went live with Wasted Time 1.0 on July 12th. It has been an exciting week, and we submitted our first update to Wasted Time to Apple on July 17th. It hasn’t made it through the review cycle yet, so we are all waiting for that to finish.
A couple of changes are planned for version 1.2, including more graphic enhancements. Can’t wait to submit.