Design Patterns in Mobile Application – Module 4

0.0(0)
studied byStudied by 0 people
learnLearn
examPractice Test
spaced repetitionSpaced Repetition
heart puzzleMatch
flashcardsFlashcards
Card Sorting

1/50

flashcard set

Earn XP

Description and Tags

Question-and-Answer flashcards covering key navigation, form, search, control, help, feedback, and affordance patterns in mobile app design.

Study Analytics
Name
Mastery
Learn
Test
Matching
Spaced

No study sessions yet.

51 Terms

1
New cards

Which navigation pattern uses a grid layout for items of equal importance (or irregular to emphasize some)?

Springboard

2
New cards

When designing a Springboard, what user-centric feature should be considered?

Personalization and customization options

3
New cards

Which navigation pattern works well for long lists with subtext and can be infinite with thumbnails?

Lists (Vertical / Infinite Lists)

4
New cards

What must every internal screen reached from a list provide?

A way to return back

5
New cards

Which navigation pattern must clearly differentiate the selected item and use recognizable icons or icons with labels?

Tabs

6
New cards

What navigation pattern is best for frequently updated content people like to browse and often uses a grid?

Gallery (Grid)

7
New cards

What is the primary purpose of a Dashboard in mobile apps?

To provide a roll-up of key performance indicators

8
New cards

What guideline prevents Dashboard overload?

Do not cram too much information onto the dashboard

9
New cards

Which navigation pattern models pages to fit an application’s metaphor and must be used with care?

Metaphor navigation pattern

10
New cards

For navigating a small number of pages with a position indicator, which pattern is recommended?

Page Carousel

11
New cards

Which navigation pattern progressively discloses more options or details via expandable items?

Expanding Lists

12
New cards

Which navigation pattern offers an “Infinite Area” for panning or zooming to reveal more detail?

Infinite Area

13
New cards

Why shouldn’t you innovate on the Sign-In screen?

Users expect familiar, quick login experiences

14
New cards

What two recovery/login options should a Sign-In screen provide?

Forgotten-password retrieval and social network login

15
New cards

For Registration/Sign-Up, how many screens are preferred and what must be prominent?

One screen; a highly visible Register/Sign-Up button

16
New cards

Name three best practices for a Comments feature.

Invite comments, clarify what’s being commented, show others’ comments over time

17
New cards

How should comments made within the current hour be time-stamped?

Display as minutes ago

18
New cards

What key elements should a User Profile highlight?

Badges and contributions to the social network

19
New cards

What should replace a blank screen in an Empty Dataset state?

An explanation and a single clear call to action

20
New cards

Why show progress in Multi-Step forms?

To let users know where they are and where they can go

21
New cards

Where should Settings reside and how should they appear?

Inside the app; clearly grouped and easy to understand

22
New cards

List six search interaction types covered.

Explicit, Auto-complete, Dynamic, Scoped, Saved & Recent, Search Form

23
New cards

Besides a cancel option, what must an Explicit Search field include?

A clear (✕) button

24
New cards

When implementing Auto-complete, what UI cue might be needed if results are delayed?

Feedback such as a loading indicator

25
New cards

Dynamic Search is best suited for what kind of datasets?

Constrained datasets such as an address book or personal media library

26
New cards

How many scoping options are considered plenty for Scoped Search?

Three to six

27
New cards

What are two key practices for Search Forms?

Minimize input fields and follow form-design conventions

28
New cards

Why is live scroll preferred over paging in Search Results?

It offers a smoother browsing experience

29
New cards

When offering sort options, what must be clearly indicated?

Which sort option is currently applied

30
New cards

What visual rule applies to On-Screen Sort controls?

Clearly show the selected choice

31
New cards

When choosing a Sort Order Selector, what guideline should you follow?

Use OS design conventions or an OS-neutral control

32
New cards

What is the recommended approach for Filter Forms?

Keep them simple—usually an onscreen filter or drawer

33
New cards

Where are Toolbar actions generally placed and how should icons appear?

At the bottom of the screen; icons must be recognizable or paired with labels

34
New cards

Why should navigation rarely be hidden inside an Option Menu?

It reduces discoverability; direct interactions are preferable

35
New cards

Give two design rules for Call-to-Action buttons.

Don’t hide them in menus; ensure high contrast and clear label

36
New cards

How should Bulk Actions like delete be handled?

Inside an edit mode with an obvious way to exit

37
New cards

What is a best practice for using Maps in mobile UI?

Provide visible markers and use as much screen space as possible

38
New cards

What should dialog content be like, and what fallback must exist?

Short; alternate access to instructions within the app

39
New cards

Where should a Tip appear and what should happen once the user interacts?

Near the related feature; it disappears after interaction begins

40
New cards

From what perspective should an app Tour highlight features, and how long should it be?

From the user’s goal perspective; short and visually engaging

41
New cards

What basic controls should demo Videos always provide?

Stop, pause, volume controls, etc.

42
New cards

What common use case exists for Discoverable invitations?

Prompting a data refresh

43
New cards

Name the three feedback types discussed.

Errors, Confirmation, System Status

44
New cards

How should error messages be written and displayed?

Plain language with a solution; shown in-screen (not modal) and clearly visible

45
New cards

What must confirmation feedback avoid?

Breaking the user’s flow

46
New cards

For System Status feedback, what user option should be offered for lengthy operations?

A cancel option

47
New cards

List the three gesture affordances covered.

Tap, Flick, Drag

48
New cards

What visual cue signals tappable controls?

Common visual cues such as shape/contrast; 3D effects used sparingly

49
New cards

What two UI cues help indicate a Flick affordance?

A page indicator and showing the edge of the next item

50
New cards

What might you add to support Drag affordance discoverability?

A recognizable handle icon or an invitation hint

51
New cards

Why is following design patterns important in mobile UI?

They ensure consistency, usability, and efficient navigation for users