×
Namespaces

Variants
Actions
(Difference between revisions)

Application startup usability

From Nokia Developer Wiki
Jump to: navigation, search
Rahulsingh1m (Talk | contribs)
(Application startup should follow these usability guidelines)
mayankkedia (Talk | contribs)
(updated image from the device and added content)
Line 1: Line 1:
 
[[Category:Mobile_Design]][[Category:Usability]]
 
[[Category:Mobile_Design]][[Category:Usability]]
 
 
 
== Application startup should follow these usability guidelines ==
 
== Application startup should follow these usability guidelines ==
 +
# Starting an application should not take much time, ideally 4-5 sec should be OK. If the application startup is taking more time, a splash screen with a progress bar should be provided.
 +
# During startup if any audio/video clip is played, the user should be able to control the sound.
 +
# High priority system events like incoming call should be given priority.
 +
# Low memory conditions should be handled properly.
 +
# By default, application should not start by its own. If the application features [[auto-start at reboot]], users should be given an option to reset this behaviour.
  
* Starting an application should not take much time, ideally 4-5 sec should be OK. If the application startup is taking more time, a splash screen with a progress bar should be provided.
+
<table>
 
+
<tr>
* During startup if any audio/video clip is played, the user should be able to control the sound.
+
    <td align="left">
 
+
'''Example of bad auto-start implementation'''<br>                   
* High priority system events like incoming call should be given priority.
+
[[Image:Screenshot0114.jpg]]
 +
  </td>
 +
    <td align="left">
 +
'''Example of giving user auto-start option on first run'''<br>                   
 +
[[Image:Screenshot0113.jpg]]
 +
  </td>
 +
  </tr>
 +
</table>
  
* Low memory conditions should be handled properly.
 
  
* By default, application should not start by its own. If the application features [[auto-start at reboot]], users should be given an option to reset this behaviour.
+
<table>
 +
<tr>
 +
    <td align="left">
 +
'''Example of good auto-start implementation'''<br>                   
 +
[[Image:Screenshot0112.jpg]]
 +
  </td>
 +
<td></td>
 +
    <td align="left">
 +
''' Example of good auto-start implementation'''<br>                   
 +
[[Image:Screenshot0111.jpg]]
 +
  </td>
 +
  </tr>
 +
</table>
 +
==Link==
 +
[[Auto-start at reboot]]

Revision as of 21:02, 30 June 2009

Application startup should follow these usability guidelines

  1. Starting an application should not take much time, ideally 4-5 sec should be OK. If the application startup is taking more time, a splash screen with a progress bar should be provided.
  2. During startup if any audio/video clip is played, the user should be able to control the sound.
  3. High priority system events like incoming call should be given priority.
  4. Low memory conditions should be handled properly.
  5. By default, application should not start by its own. If the application features auto-start at reboot, users should be given an option to reset this behaviour.

Example of bad auto-start implementation
Screenshot0114.jpg

Example of giving user auto-start option on first run
Screenshot0113.jpg


Example of good auto-start implementation
Screenshot0112.jpg

Example of good auto-start implementation
Screenshot0111.jpg

Link

Auto-start at reboot

33 page views in the last 30 days.