Editing Legacy Maemo 5 Documentation/Human Interface Guidelines/Reality Checks
Warning: You are not logged in.
Your IP address will be recorded in this page's edit history.
The edit can be undone.
Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 1: | Line 1: | ||
- | + | =Reality Checks= | |
- | + | The sections in this chapter give advices on how to make your application even more usable when it can already be tested. Other very useful checks can be found in the GNOME HIG [http://library.gnome.org/devel/hig-book/2.26/reality-checks.html.en Checklists Section]. | |
- | The sections in this chapter give advices on how to make your application even more usable when it can already be tested. | + | |
==Hardware Keys== | ==Hardware Keys== | ||
- | + | Check the keys of the mobile device you're testing your application with to see they could be assigned any functions already existing or new functions. This way you might find out that some actions by not need an actual control on screen as they could be assigned to a commonly used hardware key. | |
- | Check the keys of the mobile device you | + | |
==Different Devices== | ==Different Devices== | ||
- | + | Given the plurality of mobile devices out there and their differences, you'll maybe find out that some features of your application do not behave as desired in one device or another. Therefore, it extremely important to be able to either test it in those devices or let those devices users give you feedback about it. | |
- | + |
Learn more about Contributing to the wiki.