Mobile App UX Principles – chp.5 Usability Hygiene(47p~48p)

In a search or refine form, user can move a slider control to set a minimum / maximum range (e.g. for prices or budgets)
When users need to set a minimum / maximum price or budget range in order to search for – or refine search results – items, use the horizontal slider control. A slider is easy to swipe horizontally and provides simple visual cues to customise this action. Things to consider:

-Values can be entered easily.
-Numbers aren’t hidden when slider is being operated (by fat fingers).
-For some range types a discrete slider with a set of stops with predefined values may be better than a continuous range – and, you could add a histogram to a discrete slider to illustrate inventory levels available in each stop.

在搜尋或篩選表單上,使用者可以利用拖動條(slider control),去設置最小/最大範圍(如設置價格或預算)

In a form, user can select times or dates from a picker control(e.g. for entering travel dates, date of birth or time of arrival)
When users need to select times or dates provide a native time and date picker control, which make selection fast and familiar, and support multiple formats
Android can display up to 3 wheels concurrently
iOS up to four wheels concurrently (each wheel displaying a value in a single category, with formats such as Date and time, Time, Date, and Countdown).

在表單上,使用者可以從一個picker control選擇時間和日期(如輸入旅遊日,出發或到達時間來看)
-當使用者需要選擇時間或日期時,可以統一使用內建的(熟悉的)picker control。
Android 顯示3個類型(年月日)
iOS 顯示4個類型(每個類型的內容,日期和時間以相同格式顯示;選取中的數值,上下方顯示遞增/遞減的數值)

In travel forms, user can select a date from a visual calendar
Especially when on mobile users are likely not to have a calendar at hand when quickly wanting to perform a task.
Make it easy for them to select the correct dates by offering an actual calendar with days of the week from which they can pick.


When app crashes it re-starts and returns the user to the last screen used(to continue where they left off)
In the event of an app crash, ensure it restarts and returns its state to the last screen used, so that the user can continue where they left off – especially if their journey involved entering data and required effort. Don’t require users to re-enter data.


1-second delay in load time can mean a 16% decrease in customer satisfaction, and 7% loss in conversions.”

On-screen content and transitions between screens appear fast and responsive (pauses frustrate and confuse users)
Ensure on-screen content and user actions – and transitions between screens – appear responsive, because unresponsive screens cause users to repeat actions or even close apps. And,are responsive you won’t need to use a progress indicator / loading spinner, which focus users on waiting instead of on the task or transition.
Onscreen considerations include:
Storing screen layout or skeletons locally (so they display immediately)
Minimising on-screen content (that needs to load dynamically)
-Optimising backend processing (to load elements in priority order, or predict what a user will need / do next and execute that task)
Using animation to create the effect of screens loading quickly and providing visual feedback of a user action

確認頁面上的內容,與使用者操作同步,可能因為頁面的停頓導致重複操作,或關閉APP。如果畫面停頓,加入效果(rogress indicator / loading spinner),給予使用者一個執行進度的回應/執行中的狀態。
盡量減少頁面上的內容(需要動態load dynamically)

User timings: if you use Google Analytics, you can measure resource load times of a specific screen (in Android and iOS apps)
Analytics Mobile Device reports – check conversion rates for different Mobile operating systems and devices

如果使用Google Analytics(分析),能測量頁面資源的加載時間(所有Android和iOS的APP)
Analytics(分析)行動裝置的報告 – 檢查不同裝置系統和設備的轉換率


Design for each native mobile platform – Android and iOS – because each has unique capabilities and visual languages, don’t replicate the web experience to apps, and don’t interrupt users.

每一行動裝置(APP)-Android and iOS應該具備獨特的使用模式及視覺感受的設計,不要利用網頁的操作方法,並可以讓使用者持續使用。

Do not mimic UI elements from other platforms(from Android to iOS and vice versa)
Each platform has a distinct set of conventions and qualities. If you replicate elements from one platform to another, you risk compromising the user experience and conversion.
For example,some platforms support buttons with rounded corners, or actions may have different behaviours, and it is these details and affordances that provide the user with a familiar and consistent experience. (see: sample of UI elements, icons, tabs, etc. from Android, iOS, and Windows Phone)


Do not use underlined links (apps use buttons NOT links)
-Avoid using text with underlined links, which are part of the web / browser / page model, and not part of the app / screen model. Apps use buttons, not links.
Do not hardcode links (to other sites or apps) Avoid hard-coding links in your app, both to sites and other apps. Hard coded links will need to be manually changed and cost you time and effort. Users navigating to broken links will have a poor experience and may abandon.


Do not take users to the browser (users’ stay in-app at all times)
Keep users in-app at all times, to maintain their geography and to optimise conversion. If your app lacks a specific feature or content, try to use an in-app browser; but do not invoke the Smartphone browser, or you will cause users to lose their geography and not return to the app, which will increase abandonment and reduce conversion.


Do not ask users to rate your app too soon after downloading it (i.e. don’t interrupt users)
Avoid interrupting users by asking them to rate your app if they’ve only recently downloaded it or only used it a few times. Instead, wait until they prove to be repeat users and they’ll be more likely to rate your app favourably and provide more informed feedback (that you can act on). You could trigger the rating request after a specific number of app openings or tasks / goals have been completed. Also, never incentivise positive ratings, as this is against store rules.

-可以設定啟動app達一定次數後,再觸發評價提示,但不要一直跳出這個提示,這違反了app store 的規定。


你的電子郵件位址並不會被公開。 必要欄位標記為 *