FlashLite UI Design
Usability and UI in mobile projects
iisilylauru. $*':4a1nIn: IIe 1492!? ‘
Usability at the heart
of development
Most developers and managers know the importance of usability
in product developmen...
Usability at the heart
of development
Maybe next time there's no need for your blood pressure to go
through the roof tryi...
Usability at the heart
of development
Do’s
oAsk for the user's input often.
oLet the user experiment.
oselect users wh...
Usability at the heart
of development
Donts
oDon’t take everything the user says as the absolute truth.
oDon’t interrup...
Usability engineering
Success in developing usable products requires that usability is
designed into the product right fr...
Usability engineering
Methods
When developing game guidelines, mobile phone game developers
were interviewed about produ...
Usability engineering
Methods
When applied to mobile application development, the usability
implementation process is di...
Usability engineering
Methods: Requirements
In the requirements phase, the concept is defined and the idea of
the appli...
Bologna, 29 gennaio 2007
Usability engineering
Methods: Design and specifications
After the concept is validated, ...
Usability engineering
Methods: Implementation
In the implementation phase, the first version of the application is
prog...
Usability engineering
Methods: Testing
The application is tested to make sure it meets the requirements
set at the begin...
Usability engineering
Methods: Testing
0 Expert analysis: Make sure the user interface is functional,
without severe f...
Usability engineering
Methods: Release
When the game has passed the testing phase, it is time to release
version 1.0 t...
Usability engineering
Methods: Maintenance
In typical application development processes, a significant portion
of the ex...
Users are essential to
Product development
Although everyone should be involved in implementing usability,
the key is us...
Focus Groups and
Usability tests
A focus group is not a usability test and vice versa. A focus
group can be very effecti...
Group testing
A more efficient way to determine user needs and evaluate the
product is group testing, a mixture of both ...
Group testing
Seven steps to produce a group test:
. Define the target group of the product
. Recruit the test parti...
The Flash 8 mobile emulator
Publish settings > select flash lite1.1. Publish movie
in: win. an-:4
n vnldxn
luv. war m...
The Flash 8 mobile emulator
Test device > device settings
oumrm v
U176" £133 15- JIUDOCS
Bologna, 29 gennaio 2007 sli...
The Flash 8 mobile emulator
Standalone player > symbian > series60 > nokia > 6630 > add
-: :nvuwo auoauwxbw
Dnotllnvltr I...
The Flash 8 mobile emulator
zwqayuzou
nor: -In in-uu: i-u. ~.upnu
V’ I“: HIpr©. 'l " 0
V5.1‘
E V9.9
Cznm-nan
Fug-no
B...
Building blocks for
a successful project
the balancing act
The primary concern in designing our application has been
int...
Building blocks for
a successful project
The balancing act
Whatever the style, the targeted user group, or content of ...
Building blocks for
a successful project
Concept container
A concept container is visual element that sums up the conten...
Building blocks for
a successful project
Basics of usability
Some basics of usability:
0The application must constantl...
Resources
UsabilityHUB [http: //www. ideanresearch. com/ usabilityhub/ index. php]
Series 60 Developer Platform 2.0: Usa...
Resources
Series 40 Developer Platform 1.0: Usability Guidelines for J2ME"‘ Games v1.1
[http: //www. forum. nokia. com/ ...
of 29

Natili Flash Usability JMDF Flash Lite vs. JavaME

Published on: Mar 3, 2016
Published in: Business      
Source: www.slideshare.net


Transcripts - Natili Flash Usability JMDF Flash Lite vs. JavaME

  • 1. FlashLite UI Design Usability and UI in mobile projects iisilylauru. $*':4a1nIn: IIe 1492!? ‘
  • 2. Usability at the heart of development Most developers and managers know the importance of usability in product development. And almost everyone is familiar with usability testing — nerve rakingly near deadline, yet so esential to the succes of the project L _ Bologna, 29 gennaio 2007 slide 2
  • 3. Usability at the heart of development Maybe next time there's no need for your blood pressure to go through the roof trying to meet a deadline. What if, instead, you made one simple change to the familiar development process: implement usability right from the get go. Here are a few basic ground rules that will help you get started: l L Bologna, 29 gennaio 2007 slide 3
  • 4. Usability at the heart of development Do’s oAsk for the user's input often. oLet the user experiment. oselect users who represent your target group. olmaglne the user's point of view. I L, Bologna, 29 gennaio 2007 slide 4
  • 5. Usability at the heart of development Donts oDon’t take everything the user says as the absolute truth. oDon’t interrupt with your opinions. oDon’t use your friends for testing — they are easily affected by your presence or opinions. ‘ -Don't be blinded by your own expertise. L _ Bologna, 29 gennaio 2007 slide 5
  • 6. Usability engineering Success in developing usable products requires that usability is designed into the product right from the start by using a methodical approach called called usability engineering L L . LL44 Bologna, 29 gennaio 2007 slide 6
  • 7. Usability engineering Methods When developing game guidelines, mobile phone game developers were interviewed about product development and their needs and practices were integrated into a single model. This model can be applied to other mobile application development as well. L __ , Bologna, 29 gennaio 2007 slide 7
  • 8. Usability engineering Methods When applied to mobile application development, the usability implementation process is divided into six steps of unequal length: : Il3.. _= ~~ ‘ L l. ... "1 . J."'_"_T""l. .l. II" T L. ‘;. l.. ’ _. ... .”“~‘ I l. ... ._. ... ‘ 4‘ ‘ [ml Jar’ Ann 12- ll End U-mil . i|r. :E (c 1. ‘lug [apt-1.‘: aly-.1: S. ll’u’». ‘ on Survey 61. : p'n' -y Cuill “Ni Gtlrfiws 6. d-"’v- ‘rill: dwll--rllrn; ind Uwlim y-mt S-1'31‘-ii’: -S--‘rm bun lm yvir Cm: Tmm: lrvf lls. >*I~-laws l: Each of these phases has recommended methods to ensure that users remain at the center of development. Bo| ogna,29 gennaio ZCU7 slide 8
  • 9. Usability engineering Methods: Requirements In the requirements phase, the concept is defined and the idea of the application is tested. To validate that the concept is viable and that the product will be usable, the product concept should be evaluated against the guidelines. Some critical element of the application idea may need to be modified or the entire concept abandoned if it is demonstrated that users can't grasp the final product idea. - End-user analysis: Find out if users are interested and if there is genuine need for the product in the market. - Guidelines: Define the specific usability requirements that must be met in order to have a usable and potentially successful product. Bo| ogna,29 gennaio ZCU7 slide 9
  • 10. Bologna, 29 gennaio 2007 Usability engineering Methods: Design and specifications After the concept is validated, the requirements for its creation are defined. Specifications include both technical and usability specifications. The way the user interacts with the application is defined, as well as the entire navigation structure of the application. o End-user analysis: Make sure that the product design fits the target group for which it is intended. 0 Guidelines: Verify that the implementation does not violate existing standards and decrease the likelihood of making errors that have been identified by earlier research. slide 10
  • 11. Usability engineering Methods: Implementation In the implementation phase, the first version of the application is programmed, the user interface is implemented, and a better picture of the final product can be formed. This phase is returned to multiple times after the testing phase. 0 Consulting: Ask a usability expert about the implementation of certain features. Costly errors can be avoided with minimal cost. 0 Guidelines: Find out standard ways of implementing certain methods and make sure the selected methods are not likely to be problems for the users. 0 Expert analysis: Receive comments on how to improve the user interface and avoid designs that will likely pose problems for the users. Bologna, 29 gennaio 2007 slide 11
  • 12. Usability engineering Methods: Testing The application is tested to make sure it meets the requirements set at the beginning of the process. If it fails, the product is taken back to the implementation phase to be fixed. This is the first phase where the product is sufficiently complete to show it to final end users and see how they react to it. Changes will probably be necessary after the first iteraction of testing and quite likely after subsequent ones as well. KL Bologna, 29 gennaio 2007 slide 12
  • 13. Usability engineering Methods: Testing 0 Expert analysis: Make sure the user interface is functional, without severe flaws, and receive concrete suggestions on how to improve it. 0 Individual testing: Find out how real end users use the application and where they have problems. Also, record information about which keys they prefer to press and which views they like. 0 Group testing: By using the application in a real group situation, multiplayer features and the ways users use them can be tested. The results may be significantly different from what was expected. Also, users may find ways to cause errors in the application use. Bologna, 29 gennaio 2007 slide 13
  • 14. Usability engineering Methods: Release When the game has passed the testing phase, it is time to release version 1.0 to the public. Research is needed to find out about market acceptance, and what parts of the application can be improved for future releases. - Satisfaction survey: To find out with any statistical accuracy which parts of the application users like and which need improvement, a satisfaction survey is needed. Also, the effects of possible usability problems can be evaluated. - End-user analysis: See how well the product fits into the market for which it was intended. Bo| ogna,29 gennaio ZCU7 slide 14
  • 15. Usability engineering Methods: Maintenance In typical application development processes, a significant portion of the expenses occur after the release of the product. The product may require changes or updates, different language versions, porting to new devices, or a new episode. 0 Group testing: How would users modify the application, what more do they want from it, what would get them to update or buy another version? - Satisfaction survey: After the application has been in the market for a while, competition may affect users’ attitudes and requirements. Also, they will have had a longer time to evaluate the application. - End-user analysis: See how well the product fits into the market for which it was intended Bo| ogna,29 gennaio ZCU7 Slide 15
  • 16. Users are essential to Product development Although everyone should be involved in implementing usability, the key is user involvement and making sure users are at the center of the development process. Let users take part in testing early and often, using suitable techniques. Measure those aspects that have special value to users and track changes to these measures over the project's duration. Don't be afraid to try new things — you can't go wrong when users are your allies, so involve them in as many project phases as possible. It's the best way to assure a better user experience and product acceptance. Remember: the user is your secret asset. Bologna, 29 gennaio 2007 slide 16
  • 17. Focus Groups and Usability tests A focus group is not a usability test and vice versa. A focus group can be very effective at getting opinions, but it has nothing to say about performance. According to usability guru Jakob Nielsen, the proper role of focus groups is not to assess interaction styles or design usability, but to discover what users want from the system. The opposite can be applied to usability testing: It is an excellent technique for evaluation, but inadequate for assessing user needs. Knowing this, imagine what these two techniques could produce together! Bologna, 29 gennaio 2007 slide 17
  • 18. Group testing A more efficient way to determine user needs and evaluate the product is group testing, a mixture of both focus groups and usability testing Group testing can provide a wealth of usable information. For example, it yields product information about the efficiency and ease-of-use of a product, as well as marketing information about consumer behavior, pricing, and models of use. In group testing, the real focus group users provide information while using the products and discussing them with their peers. In addition to offering feedback about new product features and qualities, the test reveals issues related to cultural usability and applicability to existing behavioral models. Further, group testing can be used for concept design and other phases of product development Bo| ogna,29 gennaio ZCU7 slide 18
  • 19. Group testing Seven steps to produce a group test: . Define the target group of the product . Recruit the test participants through various channels . Arrange the test situation, tasks and questions . Actual group test . Analyze the results . Write the report . Report the results to product developers lOU1-bL: Jl)l-5 Bo| ogna,29 gennaio ZCU7 slide 19
  • 20. The Flash 8 mobile emulator Publish settings > select flash lite1.1. Publish movie in: win. an-:4 n vnldxn luv. war mun mu-mr. cw: :7». . . 'm mac. :1 2: xi _lpJ my: an r-um! aoatmmnrv» sauna mat 1.Ie-mawim» ‘In: -ueieu :1-axial u out o- -Aewbau lo once an rod ac. -u i. §.Zl. §l. .£l. &j. L D - lab Bologna, 29 gennaio 2007 slide 20
  • 21. The Flash 8 mobile emulator Test device > device settings oumrm v U176" £133 15- JIUDOCS Bologna, 29 gennaio 2007 slide 21
  • 22. The Flash 8 mobile emulator Standalone player > symbian > series60 > nokia > 6630 > add -: :nvuwo auoauwxbw Dnotllnvltr In - mun! man-on: -. nu HIJ nu luau» -alfififlli --aw». ‘ Ito-aim I no. no I no 4 arm I aw a um I on. ;.. '.:1i 0‘ Ilduausu J cob. ..-mi I Iu. u.. in ‘ nuns: ‘‘ I0)v¢? I.-ltI -* Witlhfnry ‘‘ Inn»-so--A 4 . g sum 0 _‘ '1‘-$1 . um. - u SOOILCI Ma! Mar 00): wanna mu‘ . An tau-1:-rinvum. -mu : , Ocualvvvuovmoo Bologna, 29 gennaio 2007 slide 22
  • 23. The Flash 8 mobile emulator zwqayuzou nor: -In in-uu: i-u. ~.upnu V’ I“: HIpr©. 'l " 0 V5.1‘ E V9.9 Cznm-nan Fug-no Bologna, 29 gennaio 2007 slide 23
  • 24. Building blocks for a successful project the balancing act The primary concern in designing our application has been integrating powerful visuals with usability. I'm sure the concept is not new to you. Infact everyone, from the most sophisticated development team to the newcomer, whether conciously or uncounciously, is confronted with this balancing act, whether he or she is developing an application or a website. L Bologna, 29 gennaio 2007 slide 24
  • 25. Building blocks for a successful project The balancing act Whatever the style, the targeted user group, or content of the application, we have identified three elements we constantly keep in mind in the delicate balancing act between visuals a usability 0Concept container oBasics of usability L Bologna, 29 gennaio 2007 slide 25
  • 26. Building blocks for a successful project Concept container A concept container is visual element that sums up the content of the application at a glance. If you go so far as to develop a an effective concept container you are half way through designing an a good application. In our sample application the concept container is the world rotating over a water drop. The key elements for an effective concept container are, intuitiveness, functionality and visual pleasentness. Bologna, 29 gennaio 2007 slide 26
  • 27. Building blocks for a successful project Basics of usability Some basics of usability: 0The application must constantly offer the user the possibility to exit the application -The application must constantly offer the user the possibility to return to the previous screen -The user must always be in control over the application work flow oFurtherrnore it is important that the application have the possibility to be executed in background L Bologna, 29 gennaio 2007 slide 27
  • 28. Resources UsabilityHUB [http: //www. ideanresearch. com/ usabilityhub/ index. php] Series 60 Developer Platform 2.0: Usability Guidelines For Symbian C++ Games v1.0 [http: //www. forum. nokia. com/ main/1,,040,00.htm| ?fsrParam=3-3- / main. html&fi| eID=4624] Series 60 Developer Platform 2.0: Usability Guidelines For J2ME"" Games v1.0 [httpz/ /www. forum. nokia. com/ main/1,,040,00.html? fsrParam=3-3- / main. html&fi| eID=4623] Series 60 Developer Platform 1.0: Usability Guidelines for J2ME"” Games v1.1 [httpz/ /www. forum. nokia. com/ main/1,,040,00.html? fsrParam=3-3- / main. html&fi| eID=4814] Bo| ogna,29 gennaio ZCU7 slide 28
  • 29. Resources Series 40 Developer Platform 1.0: Usability Guidelines for J2ME"‘ Games v1.1 [http: //www. forum. nokia. com/ main/1,,040,00.html? fsrParam=3-3- / main. html&fi| eID=4813] Series 40 Developer Platform 1.0: Compatible Devices from Game Developer's Point of View v1.1 [httpz/ /www. forum. nokia. com/ main/1,,040,00.html? fsrParam=3-3- / main. html&fi| eID=4812] Game Playability Top 10 Tips [http: //www. forum. nokia. com/ series40_game_usabi| ity_study - tips] Series 40 Games Usability Study [httpz/ /www. forum. nokia. com/ series40_game_usabi| ity_study] Bo| ogna,29 gennaio ZCU7 slide 29

Related Documents