1. Apple Iphone Woubshet Nema Bethelhem Tadele

2.  This is a presentation about AppleIphoneguidelines  Woubshet Nema k8newo00@students.oamk.fi  Bethelhem Tadele, k8asbe00@students.oamk.fi k8asbe00@students.oamk.fi

3. The apple style guideline describes guideline and principles that help to design a superlative,user interface and user experience for your iOS app.

4.  You can use a navigation bar to enable navigation among different views, or provide controls that manage the items in a view.  Use the title of the current view as the title of the navigation bar.  Make sure it’s easy to read the text in the navigation bar.  Consider putting a segmented control in a navigation bar at the top level of an application.  Avoid crowding a navigation bar with additional controls, even if there appears to be enough space.  On iPhone make sure your custom navigation bar icons fit well in the thinner bar that appears in landscape orientation. Don’t specify the height of a navigation bar programmatically

5.  You have control over the font, color, and alignment of the text in a text view, but only as they apply to the entirety of the text.  you can’t change any of these properties for only part of the text.  The default font is the system font and the default color is black, because these tend to be the most readable.  The default for the alignment property is left (you can change this to center or right).

6. .Usually use blue color for icons The IOS provides standard button and icons To avoid confusing people, never use the standard buttons and icons to mean something else. Create different sizes of your application icon for different devices (57 x 57 pixels, 114 x 114 pixels (high resolution)) Rounded corners Drop shadow Reflective shine

7.  Create edit menu items that edit, alter, or otherwise act directly upon the user’s selection  Users can reveal an edit menu to perform operations such as Cut, Paste, and Select in a text view, web view, or image view.  Display commands that make sense in the current context.  Support both gestures people can use to invoke the menu.  Avoid creating a button in your UI that performs a command that’s available in the edit menu.

8.  Mobile users have neither the time nor the desire to read through a lot of help content before they can benefit from an application. What’s more, help content takes up valuable space to store and display.  iOS-based devices and the built-in applications are intuitive and easy to use, so people don’t need onscreen help content to tell them how to use the device or the apps.  Make Search Quick and Rewarding

10.  Elevate the Content People Care About  Think Top Down  Give People a Logical Path to Follow  Make Usage Easy and Obvious  Use User-Centric Terminology  Minimize Required Input  Downplay File-Handling Operations  Enable Collaboration and Connectedness  De-emphasize Settings Avoid including settings in your application if you can.