3 ms·

Will Apple accept it? As I remember (not being an app store developer I don't really know), apps that duplicate built-in functionality are not allowed.

by miahi 14y ago

pilif 14y ago
This rule has been removed quite a while ago. How else would you think that we would see Google Chrome on iOS. Or Sparrow (duplicates Mail.app) In fact, in their apology for the maps disaster, apple specifically recommended downloading map apps from other vendors (and they even feature a alternative maps category on the AppStore ATM). As such I would believe it's highly likely that they would accept a Google Maps app.
- jakejake 14y ago
  There is still a rule in the guidelines that mentions "Apps that duplicate Apps already in the App Store" though it doesn't specify whether those apps are Apple's own, or any other developer (in fact, comically, the rule lists "fart apps" as an example). They don't really say how many apps of a certain type will be accepted into the app store before this rule goes into affect. They also have rules against "Apps that look similar to Apps bundled on the iPhone", "user interfaces that mimic any iPod interface" and "Apps which appear confusingly similar to an existing Apple product" I think basically the guidelines are written to allow Apple to reject apps with it's own discretion when it doesn't want them in the store. Whether that be for business reasons or otherwise. In the case of map apps, they seem to be rather lenient. I wonder if that's more of a grandfather type situation because they didn't have their own map app before iOS6.
jakejake 14y ago
The rules that Apple applies are sometimes mysterious and seem to evolve over time. They seem to have certain areas that they block competition, but others where they seemingly don't care. Map apps seem to be ok, but apps that step on the toes of other iOS features get rejected. If you read the app store review guidelines, it is actually written in a very casual, comical tone where they try to explain the personal nature and gray area of app guidelines. However I'm sure it's not funny for those developers who's apps are rejected. https://developer.apple.com/appstore/resources/approval/guidelines.html https://developer.apple.com/appstore/resources/approval/guid...
- buster 14y ago
  My bet: Map apps are ok as long as there is no competition from Apple. Let Apple build up their maps app and the stance will change.
  - jakejake 14y ago
    I bet if Apple had written their own map app from the beginning then all third-party map apps would all be restricted to using the iOS map engine - the same way third party browsers are limited to using the webkit engine.
    - pooriaazimi 14y ago
      Well, there are sound technical reasons as to why 3rd party apps aren't allowed to use Nitro. The same cant be said about a Maps engine.
      - buster 14y ago
        Which would be?
        pooriaazimi 14y ago
        3rd party apps aren't allowed to sign dynamically-loaded code (which almost everyone agrees is a big security WIN, even if it sucks a little). Saurik (creator of Cydia): Apple can't turn on the ability to do executable, dynamically written to memory pages just for their library: they'd have to turn it on for the entire process, at which point you could also do crazy things like download native code and execute it, bypassing the entire concept of their "codesign" mechanism. http://news.ycombinator.com/item?id=2338338 http://news.ycombinator.com/item?id=2338338 Jail breakers can enable Nitro for other apps (like Google Chrome) by using a utility called Nitrous.
        buster 14y ago
        What i know is that every other OS on the earth allows that. To me it sounds just like a convenient excuse :) Easier to say "blabla security blabla" instead of "we shut down apps because we don't want competition". Even if it is true that it increases security somewhat. I'd vote for more "freedom" instead of a more restricted environment.

Will Apple accept it? As I remember (not being an app store developer I don't really know), apps that duplicate built-in functionality are not allowed.

by miahi 14y ago

Will Apple accept it? As I remember (not being an app store developer I don't really know), apps that duplicate built-in functionality are not allowed.

pilif 14y ago

This rule has been removed quite a while ago. How else would you think that we would see Google Chrome on iOS. Or Sparrow (duplicates Mail.app) In fact, in their apology for the maps disaster, apple specifically recommended downloading map apps from other vendors (and they even feature a alternative maps category on the AppStore ATM). As such I would believe it's highly likely that they would accept a Google Maps app.

jakejake 14y ago
There is still a rule in the guidelines that mentions "Apps that duplicate Apps already in the App Store" though it doesn't specify whether those apps are Apple's own, or any other developer (in fact, comically, the rule lists "fart apps" as an example). They don't really say how many apps of a certain type will be accepted into the app store before this rule goes into affect. They also have rules against "Apps that look similar to Apps bundled on the iPhone", "user interfaces that mimic any iPod interface" and "Apps which appear confusingly similar to an existing Apple product" I think basically the guidelines are written to allow Apple to reject apps with it's own discretion when it doesn't want them in the store. Whether that be for business reasons or otherwise. In the case of map apps, they seem to be rather lenient. I wonder if that's more of a grandfather type situation because they didn't have their own map app before iOS6.

jakejake 14y ago

The rules that Apple applies are sometimes mysterious and seem to evolve over time. They seem to have certain areas that they block competition, but others where they seemingly don't care. Map apps seem to be ok, but apps that step on the toes of other iOS features get rejected. If you read the app store review guidelines, it is actually written in a very casual, comical tone where they try to explain the personal nature and gray area of app guidelines. However I'm sure it's not funny for those developers who's apps are rejected. https://developer.apple.com/appstore/resources/approval/guidelines.html https://developer.apple.com/appstore/resources/approval/guid...

buster 14y ago
My bet: Map apps are ok as long as there is no competition from Apple. Let Apple build up their maps app and the stance will change.
- jakejake 14y ago
  I bet if Apple had written their own map app from the beginning then all third-party map apps would all be restricted to using the iOS map engine - the same way third party browsers are limited to using the webkit engine.
  - pooriaazimi 14y ago
    Well, there are sound technical reasons as to why 3rd party apps aren't allowed to use Nitro. The same cant be said about a Maps engine.
    - buster 14y ago
      Which would be?
      - pooriaazimi 14y ago
        3rd party apps aren't allowed to sign dynamically-loaded code (which almost everyone agrees is a big security WIN, even if it sucks a little). Saurik (creator of Cydia): Apple can't turn on the ability to do executable, dynamically written to memory pages just for their library: they'd have to turn it on for the entire process, at which point you could also do crazy things like download native code and execute it, bypassing the entire concept of their "codesign" mechanism. http://news.ycombinator.com/item?id=2338338 http://news.ycombinator.com/item?id=2338338 Jail breakers can enable Nitro for other apps (like Google Chrome) by using a utility called Nitrous.
        buster 14y ago
        What i know is that every other OS on the earth allows that. To me it sounds just like a convenient excuse :) Easier to say "blabla security blabla" instead of "we shut down apps because we don't want competition". Even if it is true that it increases security somewhat. I'd vote for more "freedom" instead of a more restricted environment.