4 ms·

I'm becoming very irritated with Apple's behavior in the app store. While it's nothing new, I hate that they're restricting apps that compete with native apps.

I'm becoming very irritated with Apple's behavior in the app store. While it's nothing new, I hate that they're restricting apps that compete with native apps. Sparrow? No push notifications for you. Dolphin? Here's an NC17 rating (wtf?) for you, and by the way-- no way to change the default browser. I'd really like to see a reasonable explanation for both of these scenarios by Apple. My guess is the only reasonable explanation is that they want to restrict and "protect" the user experience for that critical functionality in a way that seems like an ornery chef who refuses to cook your steak medium well.

Xuzz 15y ago
I tried to explain it here: http://news.ycombinator.com/item?id=3707183 http://news.ycombinator.com/item?id=3707183 More condensed, it's a combination of Apple not wanting each app re-implementing push (or constant polling), Sparrow not willing to take on the responsibility of being able to access your email, and Google not providing low-privileges access for Sparrow to only be able to see the little amount of data that push needs.
Terretta 15y ago
Apple's happy to let Sparrow use push. Sparrow didn't want to use push, they want to poll. Allowing that would be good for time-pressed or unskilled devs, but bad for users. Sparrow admittedly doesn't want to figure out how to do push securely. But look at the fantastic PushMail app (dopushmail.com) to see a beautiful push implementation. Apple's not blocking push. // Too bad about dopushmail.com having to stop selling the app. That leaves an opportunity for someone...