Module 9

Question 1

Workflows

Answer 1

Sequence of activities that take place to complete a specific task or job

Presented in UX as a process of screens / screen states

Question 2

Registration

Answer 2

How to improve registration:

1. Don’t force registration unnecessarily
2. Don’t force registration with a social media account
3. Explain why you are asking for personal details when registering
4. Use inline validation when getting users to register (good first impression)

Question 3

Onboarding

Answer 3

Onboarding is to:

1. What the app does
2. How to use it

If product is simple and adheres to a recognised mental model - no onboarding is necessary

No onboarding should be the default

Question 4

When to consider using onboarding

Answer 4

1. Product requires users to develop a new mental model
2. Product is complicated
3. If the product requires users to enter data immediately
4. If the product has recently been redesigned and there have been a lot of change

Question 5

Onboarding objectives

Answer 5

1. Get users to engage with the app as quickly as possible
2. Make the initial engagement as smooth and as friction free as possible
3. Answer critical questions upfront: 1.What does it do? How does it work?
4. Answer deal-breakers (how much does it cost? how do I pay)

Question 6

Onboarding styles: Static Walk Through

Answer 6

1. Keep them short and concise
2. Use images and minimal text
3. Give users the option to skip them

Question 7

Interactive walkthrough

Answer 7

Getting the user to interact with the product as you explain / demonstrate functionality is far better than a static walkthrough

1. Get the users to use the services while demonstrating the benefits
2. Address any dealbreakers as they register

Question 8

Tutor overlays

Answer 8

Explain how a product works and how to access certain features

Question 9

Contextual hints

Answer 9

only providing help when needed

Question 10

Onboarding Summary

Answer 10

1. Be sure that onboarding is necessary before implementing it
2. Define the key messages
3. Define the key features to get people started
4. Interactive walkthroughs are more beneficial for outlining benefits
5. Tutor overlays are better for explaining features

Question 11

Sign in

Answer 11

How to get sign in right:

1. Keep users logged in (so they don’t have to sign in repeatedly)
2. Show don’t hide passwords as they sign in
3. Use finger print or face id to make the sign in process as quick and simple as possible

Question 12

Benefits of biometric id

Answer 12

1. Quick and convenient
2. User can’t forget a fingerprint or face
3. No more fiddling about with keyboards
4. No more password recovery or resets

Question 13

Complex forms

Answer 13

Best way to build complex forms:

1. Structure as a conversation
2. Minimise inputs
3. Use smart defaults

Question 14

Making complex forms conversational

Answer 14

Follow this structure when making long complicated forms:

1. Tell the user something
   THEN
2. Ask the user something

Repeat

Question 15

Structuring complex forms

Answer 15

1. Top align labels: to aid scanability and reduce user work
2. Use single columns: aid scanability (easier to scan top to bottom) (including check boxes)
3. Use field length as an affordance: if user is only required to fill in a small amount of information shorten the field
4. Avoid aestrix / optional fields: only essential fields should appear on a form
5. Use descriptive labels on buttons: instead of ‘Submit’ use ‘Start your plan today’
6. Use steppers / progress bars: Show how much progress has been made in a form / how many steps are left

Question 16

Payment: Follow a conventional payment flow

Answer 16

1. Remind the customer what they are buying and how much it costs - make payment amount very clear
2. Provide them with a payment form where they can enter their details
3. Next provide them with a confirmation that there payment is being made
4. Confirm that the transaction is complete and payment has been successful

Question 17

Minimise questions

Answer 17

Don’t ask unnecessary questions: only ask the bare minimum of what is required to minimise taps

Question 18

Basic Payment Screen

Answer 18

1. Name on card
2. Card number
3. Expiry date
4. Security code (CVC)

Question 19

Use auto-formating

Answer 19

Chunk phone numbers

e.g 0862021093

086 202 1093

Easier for users to fix errors then

Question 20

Increased security perception

Answer 20

1. Display credit card options - there is a halo effect of your brand being associated with well know credit card companies
2. Confirm payment amount (make it very obvious)
   Repeat it again for the payment button “Pay $20” to reduce ambiguity
3. Use padlock icons on card number fields - gives the impression to user that thing are more secure
4. List payment processor : gives halo effect

Question 21

Microtasks (or modes)

Answer 21

Micro-tasks: Add content or data to your app / edit pre-existing content

E.g adding a new city to your weather app

1. Performing a specific function
2. Interface changes entirely (focuses only on micro-task)
3. Navigation/content are typically removed

Question 22

Micro-tasks (Summary)

Answer 22

1. Micro-tasks are often the only tasks for single use case applications
2. Only way to manipulate content for many apps