0

Apple's announcement of the 'Optimized for iOS7' mandate is as follows:

https://developer.apple.com/news/index.php?id=12172013a

Starting February 1, new apps and app updates submitted to the App Store must be built with the latest version of Xcode 5 and must be optimized for iOS 7. Learn more about preparing your apps by reviewing the iOS Human Interface Guidelines.

There's been several questions regarding this already regarding the Xcode part, which seems fairly straight-forward (use Xcode 5!)

But the 'optimized for' part along with the HIGs is much more vague.

It appears that some interpret this to mean "It has to look like a native iOS7 app...Helvetica Thin, extremely flat icons, translucency, etc"

But I find that hard to accept given how broad app UIs tend to be. I don't see EA Sports changing all their UIs to match, for example. Has apple published any clarifying documentation in regards to what they mean by 'optimized for' and how closely the UI must adhere to iOS7 conventions and to what range of apps this would apply to (all apps? Only native apps? HTML5 apps? Games? etc.)?

DA.
  • 36,871
  • 47
  • 133
  • 201
  • It's difficult to see how this fits within the 'specific, answerable problems in software development' brief that governs content on [so]. –  Jan 22 '14 at 00:26
  • @MikeW I don't disagree, actually...mainly due to it being hard to answer given out vague Apple is about it. :/ That said, if apple does have more detailed documentation, that would be an answerable aspect. – DA. Jan 22 '14 at 01:06
  • This can't be answered here, as only Apple knows, and they choose to be purposely vague (random theories include perhaps for legal reason or to leave border cases regarding an app to the judgement of the reviewers, etc.) – hotpaw2 Jan 23 '14 at 06:49

2 Answers2

1

Coming from someone who has submitted a lot of apps, this isn't something I would see Apple enforcing unless you stray very far from the iOS 7 look and feel.

For example, I could imagine someone trying to submit an application that looks & feels a lot like an iOS 6 app, which is something they wouldn't want (confusing). Or, imagine somebody creating a new UIDatePicker that looks like the iOS 6 date picker (confusing). They're simply looking for consistency.

So, rule of thumb when it comes to HIG--use what apple provides. For custom views, respect the platform and don't confuse the user.

More specifics https://developer.apple.com/appstore/resources/approval/guidelines.html

David McGraw
  • 5,077
  • 7
  • 32
  • 35
  • I tend to agree with you...just wish Apple was a bit more specific with details. – DA. Jan 22 '14 at 01:07
  • Sadly a lot rests on the judgement of reviewers. I've been rejected for some wild/subjective reasons before. For example, I built a mail app and used their own activity indicator. The reviewer found that to be confusing w/ their own mail app and rejected it. We had to re-design the pull to refresh view. I've also had an app (split into 2 apps) where an iPad version of my app was rejected, and the (same app) iPhone version approved! Case-in-point: build, submit & pray. – David McGraw Jan 22 '14 at 01:28
1

One current completely unsupported working hypothesis seems to be that, as of Feb 1st, an iOS app has to be built with the iOS 7 as Base SDK, and that the newer iOS 7 metrics can't break anything in the UI (as in non-operable buttons or alerts, views partially-hidden under the status bar or behind tool bars, text half off-screen, etc.), and the app can't attempt to call any deprecated APIs removed from iOS 7.

hotpaw2
  • 68,014
  • 12
  • 81
  • 143