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.
We just updated our SSL certificates. But because Nirvana uses html5 offline caching, and because Chrome (erroneously) caches SSL credentials, we needed to trigger a cache refresh from our servers. You will see the “Nirvana has been updated… please reload!” message. Reload and all will be good.
(There wasn’t really an update, but this was the best way to get everyone’s offline cache up to date)
Note to Safari users: sorry you got caught up in this workaround for Chrome… there really was no need to refresh your cache, but we didn’t have a way to target only the Chrome users. Oh the internets…
Hello Internet Explorer users -
David managed to track down the mystery of why N2 is not syncing properly for Internet Explorer users. It turns out that there is a known bug in Chrome when used as a Chrome Frame inside Internet Explorer.
Ajax network requests silently fail (requests never make it out to the server) under certain conditions, and as a result the nirvana servers are never notified of changes you make to your data. N2 is smart enough to realize that you have “unsaved items” — the prompt that comes up if you try to logout after making changes to your data — but because Chrome Frame isn’t actually sending any data to nirvana servers, N2 effectively runs offline forever, and thus your changes are not reflected when you access N2 via another device.
BOTTOM LINE — Don’t use Internet Explorer. Use the standalone Chrome Browser instead, at least until the Google team releases a fix.
Google Chrome Browser http://www.google.com/chrome
Google Chrome Frame http://code.google.com/chrome/chromeframe
Chrome Frame Bug http://code.google.com/p/chromium/issues/detail?id=76439
ChromeFrame 12 (12.0.742.100, file date 13-Jun-2011) now appears to be working in IE 8 / 9, based on a limited amount of testing.
Time for a rant. It’s just gonna make me feel better.
So, the day we decided to ditch Internet Explorer 6 and 7, there was much rejoicing around the office, agency colleagues would exclaim, “What? You only have to test for IE8 compatibility?!” and in our pity the next round of beers would wind up on our tab.
I think not. This is 2010. Not 2001.
Truth be told, IE8 doesn’t know it’s ass from it’s elbow with some perfectly valid web pages from 2001. But I digress.
Safari and Chrome are gems. Opera too. They do just about everything right and they don’t break a sweat doing it. Firefox, while not the zippiest of browsers, at least does what you tell it. Internet Explorer? …endless code rewrites just to keep it from yacking up all over itself. Recently, IE8 has started bitching about some Nirvana js code, saying “A script on this page is causing Internet Explorer to run slowly. If it continues to run, your computer may become unresponsive. Do you want to abort the script?” Uh, no sir… I’d like you to run the script. That’s why we wrote it. Dear Microsoft, how about fixing Internet Explorer rather than tossing a warning at the user? It’s not like any other browser has a problem with doing what’s asked of it. There’s even a support page on the subject, though it reads suspiciously as though the message only pops up when there’s a problem with the website, not with the browser. Makes us look bad even though we’re doing things right. Nice.
So, we’ll continue to slug away, rewriting perfectly acceptable code, yet again, to run under the lowest-common-denominator browser that is IE8… but what a waste of time and resources. Considering that every other browser on planet earth thinks Nirvana is just peachy, is this really not just the IE guys passing the buck?
Man, life is too short. Ok, back to work…