I wish I was surprised, but this seems to happen with a lot of OS-extending apps on the iOS device. I've never heard of a game being banned from the app store, but as soon as it's something that Apple doesn't already have baked into the operating system... It's been said before and it'll be said again: Playing in Apple's walled garden isn't a safe way to make a living.
Apple copies rejected app
21–30 of 71 posts
Re: Apple copies rejected app
#22Earlier quoted context omitted.
I would guess that 99% of the outrage stems from the similarity of the icons.
I dunno, the headline is "Apple copies rejected app" not "Apple copies rejected app icon". Seems to me that people either don't know how the App Store and its requirements work, or they're just want to be outraged at Apple. Edit: It seems to me that even people commenting here in HN don't realise that the App Store guidelines don't allow for an app to take this kind of access. The icons are similar (despite how shitt…
I actually don't think anything about it is a big deal. Someone made an app that should have been an OS feature, Apple rejected it for using undocumented APIs, Apple builds the thing that should have been an OS feature, and Apple haters use this sequence of events as evidence that Apple is Evil.
It's basically the same thing as when people enabled multitasking on jailbroken iPhones and then Apple implemented it. Did they "steal" the idea of multitasking?
Re: Apple copies rejected app
#23I guess they considered it to slow and unreliable in the past to activate it for the iPhone, maybe the iCloud concept, faster processors and wireless networks led to their decision activate it in iOS5.
Re: Apple copies rejected app
#24Easily the greatest bullshit i've ever read. This cydia tool was just a hack that activated functions already in place in iTunes and iOS. Just have a look at the 1st gen Apple TV wich had wireless syncing to iTunes since 2006. I guess they considered it to slow and unreliable in the past to activate it for the iPhone, maybe the iCloud concept, faster processors and wireless networks led to their decision activate it…
Re: Apple copies rejected app
#25I wish I was surprised, but this seems to happen with a lot of OS-extending apps on the iOS device. I've never heard of a game being banned from the app store, but as soon as it's something that Apple doesn't already have baked into the operating system... It's been said before and it'll be said again: Playing in Apple's walled garden isn't a safe way to make a living.
As a developer it is probably not a good idea to use private APIs to implement a feature that has obviously been on the roadmap since day 1.
Re: Apple copies rejected app
#26So to get this straight: the guy who took Apple's icon for syncing and added a wifi symbol thinks Apple ripped him off taking their icon for syncing and adding a wifi symbol? Who'd a thunk.
Re: Apple copies rejected app
#27I wish I was surprised, but this seems to happen with a lot of OS-extending apps on the iOS device. I've never heard of a game being banned from the app store, but as soon as it's something that Apple doesn't already have baked into the operating system... It's been said before and it'll be said again: Playing in Apple's walled garden isn't a safe way to make a living.
In many cases I think it boils down to "we reject your app because not only we have thought about this use case already but we have a solution in the works, and while it's not ready yet it will probably blow anything else you would have thought about because we know the system in and out, so your app would be dead a few months from now anyway. As you're doing an impressive work on it maybe you can join us to contribu…
Re: Apple copies rejected app
#28I tried this app in the past. It was very....slow. Which is why I think Apple rejected it. Their syncing protocol, even over USB, was painfully slow. Over wifi it was dreadful. Apple has a, "do it right or don't do it at all", philosophy. They seemed to have fixed USB syncing in 4.3 because it takes me less time than before. I'm fairly confident that if he submitted his app after 4.3 was released it probably would ha…
I think it's far more likely it was rejected because it uses private APIs and takes lower-level access than App Store guidelines allow.
It was rejected because Apple changed the rules mid-game
Re: Apple copies rejected app
#29Earlier quoted context omitted.
I think it's more fair to say that making things that should/could be OS features isn't a safe way to make a living. Or if you do want to risk it, just be aware that you should have a fallback plan.
Absolutely! I develop Mac window management apps and every time a new OS is released I half expect Apple to come and wipe out my product line.
Re: Apple copies rejected app
#30Earlier quoted context omitted.
I think that's the main point is that he created an app that was probably declined because it used private APIs (or required root access?). Also: he produced the first public implementation of what? A wireless syncing software? iSync on OSX came a while before that and I'm sure there have been quite a few before that.
Mhm, so I don't understand why he expected anything different or why people are so outraged it was rejected — that's one of the major benefits of the App Store: sandboxing and access restrictions of apps. Yeah, as far as I know it was the first publicly-released wireless syncing software designed to let you sync iTunes and iOS.