It’s time for the long overdue update on whats happening with Android.
After some discussion, and looking at where we’ve got to with Android to date, we’ve decided to abandon the current direction we were taking with the Android app. Instead, we’ve decided to go with the fine folks at WhereCloud to develop the Android version of Nirvana.
In the end, it is the right choice, and should lead to a stronger product on that platform. Thanks to all the beta testers to date who have shared feedback with us. For those of you on Android, you can continue using the beta if it helps you out on your day to day.
While we’re loath to give dates, I can tell you the timeline currently on the boards should see a v1.0 in about 2 months, barring any major hiccups.
We’re happy to announce that we’ve created a new forum for hanging out and discussing all things nirvana, gtd, life/work balance and more.
Think of the new forums as the local pub/cafe where Nirvana fans and the Nirvana team come to hang out and chat, exchange ideas, ponder the state of the world, discuss both deep and frivolous topics, and occasionally blow off some steam. A lot of product ideas get hatched here. Sound like fun? Come join us!
Mitch started a discussion in the forums about where we stand re: mobile apps. I thought it would be good to cross-post this here for those who want to be in the know, but might not normally participate in the discussion forums. -Elbert
January 16, 2012 @ 07:26 PM via web
There’s been a lot of talk about development scheduling of the iPhone, Android & iPad version of Nirvana app. I’d like to share a bit of the thinking behind the approach we’re taking. I’ve recently come on board, and am initially working on the mobile app side of things.
A quick post to keep folks abreast of N2 and recurring tasks…
First: hats off to all those who have ever had to tackle this problem. It’s a lot harder than it looks. We keep getting close to the finish line and then find some edge case where our “next date” calculations break down.
Second: another humble bow before those who actually managed to create an interface that didn’t confuse the heck out of non-programmers.
Third: a few days ago we went back to the drawing board to simplify our recurring engine, and it looks like we may finally have a winner. Just finished merging this into trunk and are refactoring surrounding code that leverages it to see if this one passes mustard. Still need to do some heavy testing to ensure we’ve got this one in the bag.
We’re making an exception to our rule about not working on weekends to keep the momentum going.
Implementing recurring tasks with disconnected devices is tricky business. We knew this going in, but wow. We’ve got it working (mostly) but not quite ready for primetime. It’s looking pretty hot though.
We’re going to keep working at it over the next few days and see if we can’t get it polished for production. Apologies that we didn’t make our Friday target.
On another note, we let ~3000 new users into Nirvana 1 today. People seem happy, and our new servers didn’t break a sweat, which makes us happy. So on that happy note, wish us well as we take a quick beer break, and then continue with ironing out the kinks and getting those recurring tasks into the wild.