Perhaps it’s just frustration speaking here, but when Apple ties my hands behind my back and lets users punch me publicly in the face without allowing me to at least respond back, it’s hard to get excited about building an app.
Perhaps it’s just frustration speaking here, but when Apple ties my hands behind my back and lets users punch me publicly in the face without allowing me to at least respond back, it’s hard to get excited about building an app.
It's hard to get excited about a developer's problems when he writes an app to access a third-party service without an API and it breaks. The moral of the story isn't that Apple's process or system is wrong, it's that he should have talked to Google before trying to screen-scrape Analytics.
That's tangential to the issue at hand: due to the long review process, and combined with the ratings system, it's a hostile environment for even a developer who is on top of bugs and support.
And that's true regardless of why the bug happened in the first place.
David Zhou - 22nd April 2009 16:32 - #
Jemaleddin, did you read the post? He says he talked to Google and they helped fixing the bug, but Apple is holding back his update, ruining his reputation. Scraping is not the issue here; the issue is his inability to push an update to customers, because Apple is holding it back for whatever reason.
This would be unacceptable on any platforms but the iPhone. It's like saying that WinZip developers cannot release bugfixes because Microsoft will hold them back.
Apple's system is broken.
Giacomo - 22nd April 2009 16:45 - #
Oh right: an iPhone application! Proprietary platform, single vendor, move on, nothing to see here, and so on.
Paul Boddie - 22nd April 2009 20:49 - #
You pointed me to this yesterday and then I stewed about it for an entire day before I broke down and wrote an entire blog post about it.
http://www.mikealrogers.com/archives/577