Insight / The journal | 110s — Page 5

Give customer messages a clear place and a clear expectation

Design in-app conversations around the service record, response expectations and practical handover.

Design a useful app even when permissions are declined

Make camera, location and notification requests specific, optional where possible and recoverable.

Make shared links and reminders open the right place in your app

Plan deep links around sign-in, unavailable content and a useful browser fallback.

Make mobile forms easier to complete with the right input

Reduce typing mistakes through appropriate controls, persistent labels and considerate validation.

Design shared-device apps for the next person who picks up the phone

Make identity, handover and unfinished work explicit on phones and tablets used by a team.

Let people resume mobile work after an interruption

Preserve the right context when calls, app switching or device restarts interrupt a task.

Make mobile sign-in fit an occasional customer's life

Reduce unnecessary account barriers while keeping access understandable and recoverable.

Design the mobile screens that appear when nothing goes to plan

Give loading, empty and error states different meanings and useful next actions.

Make mobile search useful when customers do not know the exact name

Support everyday vocabulary, visible filters and recoverable no-result states.

Earn app retention by making the next visit easier

Measure recurring customer value instead of manufacturing reasons to open the app.

Design account deletion as a clear customer exit

Explain consequences, verification and completion without making customers navigate an obstacle course.

Prepare an app-store submission that reviewers can understand

Align the working app, listing and review information before planning a public launch.