StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>Well no, it doesn't necessarily mean that if your apps are running in iOS7, it needs to immediately have the new look. You can use iOS 7.0 as your base sdk but you need to do a custom modification in your app to implement the look and feel of iOS5/6 (but this is a tedious process...not recommended). Using 7.0 SDK will transform all appearance of UI Objects into iOS 7.0 objects (flat, no bezels, borderless, etc). </p> <p>If you aren't ready yet to accept iOS 7 design in your application, you can still build your app using iOS 6.1 SDK. This will retain the previous look and feel of iOS UI, and will still run on iOS 7. Be careful though, some fonts (like Hirakaku pron) change their line spacing when they are run in iOS 7 (even though it is compiled against iOS 6.1). You may wanna do a forward compatibility check in iOS 7 for your iOS 6.1 Base SDK application.</p> <p>(<strong>Cons of using iOS 6.1/6.0 as Base SDK</strong>: We still do not know if (or when) Apple will restrict submission of apps into iOS 7 only. But for now, uploading apps in iOS 6.1/6.0 is still ok.)</p> <p><strong>Summary:</strong></p> <p><strong>Using iOS 7.0 as Base SDK:</strong> (Use Auto-Layout to properly design your objects)</p> <ul> <li>When you run application in <strong>iOS 7.0 device</strong>: UI objects will appear flat (<strong>NEW UI LOOK</strong>)</li> <li>When you run application in <strong>iOS 6.1 device and below</strong>: UI objects will retain their <strong>OLD LOOK</strong> </li> </ul> <p><strong>Using iOS 6.1/6.0 as Base SDK:</strong> </p> <ul> <li>When you run application in <strong>iOS 7.0 device</strong>: UI objects will retain their <strong>OLD LOOK</strong></li> <li>When you run application in <strong>iOS 6.1 device and below</strong>: UI objects will retain their <strong>OLD LOOK</strong> </li> </ul>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload