We submitted our app for review on June 29 then waited for about 10 days before Apple started actually reviewing what we’d submitted. Perhaps everyone there went on vacation for the July 4 weekend.
This week it’s been back and forth with them trying to explain why we require an email address as part of the registration process for new users.
Apple’s stance is that a simple username should suffice.
Now, looking at the Nirvana iOS app in isolation you can (sort of) see why they are barking about this… spammers and privacy concerns and such. Clearly they are not factoring in the whole Nirvana web-app / multi-device / cloud sync eco system. (Evernote, anyone?) They don’t know who we are so they are being risk-averse and conservative.
Adding to the frustration is that we make our case and then wait a full day for a response. Apple says no again, so we make our case yet again with more backing arguments, and wait another day for a response… and round and round we go.
The list of productivity apps that require email address as part of registration is pretty significant, and all of the major players need this for, if nothing else, password recovery. Pretty standard stuff you’d think.
I’ve been patiently letting this process play out as these seem to be the normal hoops everyone goes through on first app submission. That said, if we don’t get the green light by end of day I’m going to call in some favors as this is starting to feel a bit ridiculous.
Thanks for your patience everyone.
The Nirvana iPhone app has been submitted to the AppStore for review … and so now we wait for Apple to approve. Fingers crossed! Major props to Mitch, our mobile lead, for getting this done (and for putting up with yours truly’s perfectionist streak), and to all of the beta testers who gave invaluable feedback along the way.
We’ll post an announcement once the app becomes available for download. :-)
N2 Build 457 went live moments ago. And in our never-ending quest to create the most enjoyable and useful app known to GTDkind, Nirvana’s got some new tricks!
Create new tasks at the TOP of a list
- via hot key combo Shift + N
- via rapid entry field with Shift + Enter
Create new tasks in the MIDDLE of a list
- by Shift + Clicking on an existing task’s drag-handle (or any whitespace)
a new task will be inserted just above the one clicked
In addition, there were a host of bug fixes which you can read about over here.
Happy weekly-reviewing everyone.
We’ve been heads down for a few weeks getting the iPhone (iPod) app ready for prime time. We’ve had more than a few inquiries as to why the silence on the blog. We tend to congregate over on the discussion forums and twitter, only to neglect our lovely blog here. Our bad.
So, here’s what we’ve been working on:
- Polishing up the iPhone app for App Store approval
- Begin porting the work we’ve done for iPhone app to Android
- Mobile web app overhaul for compatibility with more devices (win, bb)
- Preliminary work on iPad app
- Preliminary work on getting references lists into the app
- Migrating support to Zendesk (a better system for our current needs)
- Integrating with Chargify for simple monthly/annual subscription plans
- Incorporating Nirvanahq, Inc as a separate entity from PLU Communications, Inc for cleaner accounting vis-a-vis Chargify
- Setting up our new merchant account for billing (dependency: Nirvanahq, Inc)
- Resurrecting our Facebook presence
- Looking into alternate sign-in for users via google, facebook, twitter
- Updating our on-ramp experience… getting started video needs to be re-done, faqs need updating etc.
We also quietly removed the need for invite codes last month, effectively making Nirvana open-signup, and have almost doubled our active user-base since that time.
We’re almost there, we’re almost there…
N2 Build 389 brings some minor but nifty additions.
- Links to evernote:// within task notes are now clickable
- Added some more font choices (calibri, tahoma, verdana…)
N2 Build 390 fixes a bug that was introduced in Build 389 where changes made on one device was not being reflected in the UI of other devices. Changes were being posted to the cloud just fine, but we’d botched the timestamp persistence in the local cache so changes from the cloud were sometimes being ignored.
NOTE: you must logout and then login for the Build 390 fix to take effect. (Local cache gets cleared on logout, and then rebuilt on login.)
QUICK FIX: N2 Build 391 fixes a rare edge case where a repeating task could yield spawned tasks named (untitled) on save … also related to timestampage that we missed in build 390.