You are on page 1of 5

Mic'ael *eap:::P', Candidate; #0 0

# < Common /asks for iP'one

Page of 5




Next Blog»


Sign Out

Michael Yeap...Ph
Search This Blog


Sunday, November 21, 2010

20101121 - Common Tasks for iPhone
Comments: Below are the common tasks of iPhone as defined by Apple Inc. It is important to understand these before going to Design Guidelines.

Mobile Learning portal [prototype] WAP Blog: Mobile Learning & Usability

Blog Archive
▼ 2010 (144) ► e!e"ber (4) ▼ #o$e"ber (%&)
Mobile 'W('')* pros & !ons Mobile P+one is "ore !on$enient t+an #oteboo, -o"p... rea/ing Bible on Mobile p+one in !+0r!+ 20101121 2 -on!ept0al3'+eoreti!al 4ra"e5or, (5i,ip... Usability 4ra"e5or, (6+a!,el) 20101121 2 !on!epts & /e7intions o7 )$al0ation res... 20101121 2 )$al0ation resear!+3"et+o/ (Patton) 20101121 2 )$al0ation *esear!+ (Wi,ipe/ia) 20101121 2 )$al0ation *esear!+ (Po5ell) 20101121 2 )$al0ati$e *esear!+ (Winsett8 #A'-9) 20101121 2 '+e Planning2)$al0ation -y!le (6o!ial*e... 20101121 2 )$al0ation *esear!+ (6o!ial*esear!+Met+... 2010112& 2 iagra" 2 4o!0s :ro0p as a ;0alitati$e ... 2010112& 2 Pee, & 4ot+ergill8 Using 4o!0s :ro0ps 7...

Chapter !andling Common "asks # Starting 45 Stopping 46 Accommodating Multitasking 46 Hosting Ads 48 Managing Settings or Configuration Options 50 Supporting Copy and Paste 5 Supporting !ndo and "edo 5# $na%ling &ocal and Pus' (otifications 5) Making *our Application Accessi%le 56 Pro+iding Searc' and ,isplaying Searc' "esults 56 !sing t'e !ser-s &ocation 5. Handling Orientation C'anges 58 !sing Sound 58 /'e "ing0Silent S1itc'23'at !sers $4pect 55 6olume 7uttons23'at !sers $4pect 55 Headsets and Headp'ones23'at !sers $4pect 60 3ireless Audio23'at !sers $4pect 60 ,efine t'e Audio 7e'a+ior of *our Application 60 Manage Audio 8nterruptions 64 Handle Media "emote Control $+ents9 if Appropriate 66 Pro+iding C'oices 66 Pro+iding a &icense Agreement or a ,isclaimer 6.

'ttp;00mic'aelyeap:%logspot:com0#0 00 0common<tasks<for<ip'one:'tml

)00 0#0 4

0ichael 1eap...PhD 2andidate: .+3+33.3 4 2ommon Tas%s for iPhone

Page . of /

2010112& 2 4o!0s :ro0p resear!+ "et+o/ (:ibbs) 2010112& 2 4o!0s :ro0p reporting ((o5a 6tate Uni$)... 2010112& 2 4o!0s :ro0p resear!+ "et+o/ ((o5a 6tate... 2010112& 2 4o!0s :ro0p 2 a <0alitati$e resear!+ (=... 2010112& > 4o!0s :ro0p resear!+ "et+o/ology (Up4ro... 2010112& 2 4o!0s :ro0p resear!+ "et+o/ology (Wi,ip... 20101122 2 ?an/ling -o""on 'as,s 7or iP+one 2 part... 20101121 2 -o""on 'as,s 7or iP+one 20101121 2 Usability & esign :0i/elines 7or iP+on... 20101121 > Apple8 iP+one ?0"an (nter7a!e :0i/eline... Prototype o7 Mobile Learning Portal@pls !riti!ise3... 20101120 2 6tart eAperiential.."obile apps & M2Lea... 20101120 2 'e!+*a/ar: Mobile 5eb /esign: plat7or" ... Mobile Learning portal [prototype] WAP Blog & )1 !lone 20101114 2 =oo8 9nline -ollaborati$e Learning... /B ay 1C #o$ 2010 Proposal3Wor, e7ense 6e"inar 2010110D 2 'ri7ono$a8 ..?oar/ing -ontent in Mobile... 5riting & s0b"itting Eo0rnal Paper...7ire2n27orget... Usability (nspe!tion -riteria 7or e2Learning Porta... Paper 7or Eo0rnal: Usability (nspe!tion -riteria 7... iE)' 2010

iPhone applications should start instantly so users can begin using them without delay. When starting, iPhone applications should: ■ Specify the appropriate status bar style. ■ Display a launch image that closely resembles the first screen of the application. This decreases the perceived launch time of your application. ■ void displaying an bout window, a splash screen, or providing any other type of startup e!perience that prevents people from using your application immediately. ■ "y default, launch in portrait orientation. #owever, if your application runs only in landscape orientation, your application should launch in landscape regardless of the current device orientation. This signals users to rotate the device to landscape orientation if necessary. ■ $estore state from the last time your application ran. People should not have to remember the steps they too% to reach their previous location in your application. Comments: That's why almost all mobile phones have a Starting animation to hide the fact that the phone does take some time for the process of starting up.

People quit an iPhone application by opening a different application. &n particular, note that people don't tap an application close button or choose (uit from a menu. &n i)S *.+ and later, and on certain devices, the ,uitting application moves to a suspended state in the bac%ground. ll iPhone applications should: ■ "e prepared to ,uit at any time. Therefore, save user data as soon as possible and as often as reasonable. ■ Save the current state when stopping, at the finest level of detail possible. -or e!ample, if your application displays scrolling data, save the current scroll position. Comments: uto saving of data at appropriate frequency is important. iPhone applications should never ,uit programmatically because doing so loo%s li%e a crash to the user. There may be times! however! when e"ternal circumstances prevent your application from functioning as intended. The best way to handle this is to display an attractive screen that describes the problem and suggests how users can correct it. This helps users in two ways: ■ &t provides feedbac% that reassures users that there's nothing wrong with your application ■ &t puts users in control, letting them decide whether they want to ta%e corrective action and continue using your application or press the #ome button and open a different application

► 9!tober (42) ► 6epte"ber (&2) ► 200C (212)

#ace$ook Ba!ge



0ichael 1eap...PhD 2andidate: .+3+33.3 4 2ommon Tas%s for iPhone

Page 5 of /

Lion Mick Yap

If certain circumstances prevent only some of your application's features from working, you can display either a screen or an alert when users activate the feature. lthough an alert doesn't allow much fle!ibility in design, it can be a good choice if you can: ■ Describe the situation very succinctly ■ Supply a button that performs a corrective action ■ Display the alert only when users try to access the feature that isn't functioning Comments: Three types of stopping: (1 !ser e"its the application# ($ %pplication &uits due to certain reasons# (' Certain features of the application does not functions.

%ccommodating (ultitasking
Create Your Badge

Thriving in a multitas%ing environment hinges on achieving a harmonious coe!istence with other applications on the device. t a high level, this means that all applications should: ) *andle interruptions or audio from other applications gracefully ) +top and restart (that is, transition to and from the ,ackground &uickly and smoothly ) -ehave responsi,ly when not in the foreground The following specific guidelines help your application succeed in the multitas%ing environment introduced in i)S *.+:

T%i""er #ollo%ers
with Google Friend Connect

■ -e prepared for interruptions, and ,e ready to resume. 0ultitas%ing increases the probability that a bac%ground application will interrupt your application. )ther features, such as the presence of ads and faster application4switching, can also cause more fre,uent interruptions. The more ,uic%ly and precisely you can save the current state of your application, the faster people can relaunch it and continue from where they left off. ■ (ake sure your !I can handle the dou,le.high status ,ar. The double4high status bar appears during events such as in4progress phone calls, audio recording, and tethering. &n unprepared applications the e!tra height of this bar can cause layout problems. -or e!ample, the 7& can become pushed down or covered. &n a multitas%ing environment, it's especially important to be able to handle the double4high status bar properly because there are li%ely to be more applications that can cause it to appear. ■ -e ready to pause activities that re&uire people's attention or active participation. -or e!ample, if your application is a game or a media4viewing application, ma%e sure your users don't miss any content or events when they switch away from your application. When people switch bac% to a game or media viewer, they want to continue the e!perience as if they'd never left it. ■ /nsure that your audio ,ehaves appropriately. 0ultitas%ing ma%es it more li%ely that other media activity is occurring while your application is running. &t also ma%es it more li%ely that your audio will have to pause and resume to handle interruptions.

Members (8)

Already a member? Sign in



,ichael -eap...)h. /andidate# %&'&''%' /ommon 0asks for i)hone

)age * of +

■ Use local notifications sparingly. An application can arrange for local notifications to be sent at specific times, whether the application is suspended, running in the background, or not running at all. For the best user experience, avoid pestering people with too many notifications. ■ When appropriate, finish user-initiated tasks in the background. When people initiate a task, they usually expect it to finish even if they switch away from your application. If your application is in the middle of performing a user initiated task that does not re!uire additional user interaction, you should complete it in the background before suspending.

"ource# Apple Inc $%&&'(. iPhone Human Interface Guidelines: User Experience. Apple Inc, Cupertino, California.
Poste/ by Mi!+ael F(69F at %:%G AM Labels: /esign g0i/elines8 iP+one8 0sability !riteria8 0sability g0i/eline

No comments:

Post a Comment

Enter your comment...

 
Sign out

Comment as:

 ichael !al"es #Goo$le%


Notify me

http#22michaelyeap.blogspot.com2%&'&2''2common tasks for iphone.html


,ichael -eap...)h. /andidate# %&'&''%' /ommon 0asks for i)hone

)age + of +

Links to this post
-reate a Lin,

#e5er Post 60bs!ribe to: Post -o""ents (Ato")


9l/er Post

http#22michaelyeap.blogspot.com2%&'&2''2common tasks for iphone.html