玩運彩練小喂

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),去設置最小/最大範圍(如設置價格或預算)
當使用者要設定一個最低到最高的預算範圍搜尋時,可以使用水平方向的拖動條,簡單利用拖曳方式來增減數字,需要考慮:
可以很容易操作。
-操作拖動條時不要隱藏數字(手指不一定能很精確的微調到正確位置)。
-對於某些類型的範圍,可以設定拖動的級距,如一個大範圍(100>200>300)會比小範圍(100>101>102)來的好。-也可以在各個級距中加入長條圖,拖動到該級距時出現說明。

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。
-在其他APP的操作上,若需要選擇時間或日期,也可以支援。
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.

當APP發生錯誤,將它重新啟動並返回所進行中最後一個畫面(在離開的地方繼續)
-在一個APP發生錯誤的情況下,確任它重新啟動,並返回其操作進行中的最後一個畫面,讓使用者可以繼續。
-特別是操作內容涉及輸入,要預估發生錯誤的可能而做好保存。

1-second delay in load time can mean a 16% decrease in customer satisfaction, and 7% loss in conversions.”
1秒的延遲(負載時間)可以降低16%客戶的滿意度,和損失7%的轉換率。

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)
優化後端處理(了解使用者的需求或下一步,優先顯示主要項目)
loading的效果可以運用動畫/特效來營造,並可給予使用者較豐富的操作回饋

MEASUREMENT
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)

如果複製了一個不符合該裝置的風格元素,你必須承擔不被使用者接受的風險,例如:
某些裝置(IOS)介面上使用較多的圓角按鈕,或各種手勢具有不同的操作。
-這些細節和操作環境,使用者已經熟悉習慣了,如果引用其它裝置的風格/操作模式,就會產生疑問或排斥使用。

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.

不要使用web的連結方式(APP使用的是按鈕)
-避免在內文中使用web的連結方式(底線),該連結是於瀏覽器/網頁使用;是不適用於APP的,APP使用的是按鈕。
避免在APP上寫死按鈕的連結(連結到其他網站或APP),如要修改一個寫死的按鈕連結需要手動也花費時間,如果連結發生錯誤,使用者可能會放棄繼續。

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.

不要中斷/跳出使用者正在執行的APP(任何時候都可以再回到上一次離開前的頁面)
-保存使用者的紀錄(任何時候),並隨時可以切換到該頁面。
-使用APP時(同時使用兩個以上),如果缺少這樣的功能,可能會導致使用者無法回到原來操作的頁面,甚至需要重新操作,這會減少使用壽命。

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。
-相反的,習慣操作該APP的使用者,會比較清楚/或許哪些部份還有進步的空間,並提出建議或更多回饋(這個時候再參考使用者評價也不遲)。
-可以設定啟動app達一定次數後,再觸發評價提示,但不要一直跳出這個提示,這違反了app store 的規定。

發佈留言

發佈留言必須填寫的電子郵件地址不會公開。 必填欄位標示為 *