4 ms·

> 10.3 Apps that do not use system provided items, such as buttons and icons, correctly and as described in the Apple iOS Human Interface Guidelines may be reje

> 10.3 Apps that do not use system provided items, such as buttons and icons, correctly and as described in the Apple iOS Human Interface Guidelines may be rejected Edit: Alright, I'm taking a slaughtering on karma. Point taken. You can implement your own widgets on iOS. Please accept my apologies to all for my original comment that I thought Google wasn't in compliance and for my misguided interpretation.

TillE 11y ago
"Apps that do not use system provided items...correctly...may be rejected"
- jasonjei 11y ago
  [deleted] - I apologize for my misguided interpretation of 10.3, you may implement your own controls. I have taken your point via moderation. To all whom I have offended, I apologize.
  - tsieling 11y ago
    The small studio I work at has shipped numerous apps with non-standard UI and we've had no problems. I think they reserve the option to reject something they find unusable or otherwise objectionable.
  - josephpmay 11y ago
    I believe, if I'm reading it right, that you can implement your own, but if you use theirs you can't use them incorrectly.
    - masklinn 11y ago
      Not even that, such a use may lead to rejection, but won't necessarily do so. Most other rules state that breach will lead to rejection unconditionally. This one is conditional because it's contextual, so that developers correctly use standard controls[0] for regular applications, but can still implement their own controls in e.g. games. There's also a fair bit of leeway for developers with their own "style" e.g. I don't think tapbots uses a single system-standard widget. [0] and their accessibility support, and "skin" changes with the system's evolution
  - k-mcgrady 11y ago
    99.9% sure your reading is not correct. I'm not sure how you read it that way actually, it seems pretty clear. If you choose to use system provided UI objects they must be used the way Apple intends them to be used. For example a user tapping a UIButton expects a certain action to take place. Using buttons to display text (not perform in actions) in place of the correct object (UILabel) would lead to rejection.
    - jasonjei 11y ago
      Got it. I have never tried submitting an app that implemented my own controls other than using the iOS supplied ones, so I'm not speaking from experience.
  - coldtea 11y ago
    >but part of me believes that if it were any publisher other than Google or Adobe, acceptance of an app that implemented its own widgets and UI contrary to the uniform look of iOS apps would be on the whims of the reviewer. There are like 300.000 apps on the App Store with their custom UI contrary to iOS look -- including truly hideous items.

TillE 11y ago

"Apps that do not use system provided items...correctly...may be rejected"

jasonjei 11y ago
[deleted] - I apologize for my misguided interpretation of 10.3, you may implement your own controls. I have taken your point via moderation. To all whom I have offended, I apologize.
- tsieling 11y ago
  The small studio I work at has shipped numerous apps with non-standard UI and we've had no problems. I think they reserve the option to reject something they find unusable or otherwise objectionable.
- josephpmay 11y ago
  I believe, if I'm reading it right, that you can implement your own, but if you use theirs you can't use them incorrectly.
  - masklinn 11y ago
    Not even that, such a use may lead to rejection, but won't necessarily do so. Most other rules state that breach will lead to rejection unconditionally. This one is conditional because it's contextual, so that developers correctly use standard controls[0] for regular applications, but can still implement their own controls in e.g. games. There's also a fair bit of leeway for developers with their own "style" e.g. I don't think tapbots uses a single system-standard widget. [0] and their accessibility support, and "skin" changes with the system's evolution
- k-mcgrady 11y ago
  99.9% sure your reading is not correct. I'm not sure how you read it that way actually, it seems pretty clear. If you choose to use system provided UI objects they must be used the way Apple intends them to be used. For example a user tapping a UIButton expects a certain action to take place. Using buttons to display text (not perform in actions) in place of the correct object (UILabel) would lead to rejection.
  - jasonjei 11y ago
    Got it. I have never tried submitting an app that implemented my own controls other than using the iOS supplied ones, so I'm not speaking from experience.
- coldtea 11y ago
  >but part of me believes that if it were any publisher other than Google or Adobe, acceptance of an app that implemented its own widgets and UI contrary to the uniform look of iOS apps would be on the whims of the reviewer. There are like 300.000 apps on the App Store with their custom UI contrary to iOS look -- including truly hideous items.