Đang chuẩn bị liên kết để tải về tài liệu:
Designing the Mobile User Experience phần 5

Vì vậy, người sử dụng máy tính để bàn sẽ sớm được một tập hợp con của người sử dụng điện thoại di động. Tất cả điều này là đúng, nhưng nó bỏ lỡ những điểm quan trọng của tính di động của người sử dụng điện thoại di động chứ không phải ngồi chăm chú vào bàn làm việc hoặc thụ động trên ghế sofa | DETAILED DESIGN RECOMMENDATIONS 91 Simulator code is frequently different from the real code so your application will behave differently. The underlying system architecture is not the same on mobile and full-sized devices so your application may behave differently even with an emulator. Devices have myriad rendering and implementation idiosyncrasies both feature and user interface that are not captured in the emulator. Using screen buttons to operate an emulated device is very artificial so usability test results will be biased towards avoiding their use. The emulator is almost certainly not the device the usability testing participant will use or is accustomed to using. User behavior sitting in front of a screen is very different from when holding a device whether in a quiet office or a crowded bar. Emulators and simulators can be used by developers for interactive debugging of logic they can be used for usability testing to understand some components of the information architecture. Do not use them for system testing unit testing or user acceptance testing. 5.5 DETAILED DESIGN RECOMMENDATIONS From the discussion in this chapter it should be clear that detailed design recommendations have to focus on a particular platform and perhaps also on a particular set of devices. Fortunately there are several good sources for design recommendations frequently called style guides. This chapter cannot provide a comprehensive list of guidelines but can give you some good suggestions on where to find recommendations. 5.5.1 Platform Providers Platform providers are the most obvious source of design recommendations as they know the development environment and design intentions intimately. In theory if applications work well the platform will be more widely adopted. In practice some providers do not provide a comprehensive set of recommendations. 92 MOBILE DESIGN PRINCIPLES Windows Mobile Design Guidelines from http www.msdn. microsoft.com MIDP 2.0 Style Guide for the Java 2 .