Skip to content
opsinjs
Edit this page

Patterns

Onboarding and first run

The minimum you may collect before the reader has seen anything of value, and how to defer everything else to the moment it earns its keep

Every question asked before the first moment of value is asked on credit, and health questions are expensive. Some frighten, some are private, and some need a piece of paper to answer.

When to use it

Use it between the reader first opening the app and first seeing something about them. A setup bar with more than four steps is a warning sign. Use something else for:

How it works

  1. Scope first. One screen says what the product does, and that it is not a medical device or a substitute for advice. Late disclosure reads as concealment.
  2. Gate every field. Answer in writing: can the first useful screen render without this? If it can, ask on the surface that needs it, where the reader sees why.
  3. Ask one question at a time, with a reason. "Why we ask: your age changes the range we compare your readings to."
  4. Name the consequence of every skip. "Skip. We will show ranges for adults generally rather than for your age." Skipping still arrives at a usable screen.
  5. Show the first value. The reader's own number comes back with no status, no range verdict and no reassurance, because a first reading is not a baseline.
  6. Defer the rest. Consent comes when a feature needs it, profile fields when a calculation needs them, and an account when something must be kept or synced.

Nothing that arrives later blocks the first value, and nothing is timed or advances by itself.

StateBehaviour
ResumedReturns to the exact question with earlier answers intact
Skipped fieldsRecorded as skipped and re-asked later in context, never on the next launch
Declined everythingAn honest screen, never a locked one with no exit

NOT IMPLEMENTED. This component does not exist in any released version of opsinjs. There is no package to install, no module to import and no props interface to generate code against. Everything on this page is a specification of intended behaviour and may change without notice. Do not write code against it.

This component is not built yet

There is nothing to render because there is nothing to install. What you can read on this page is the specification the implementation will have to satisfy.

PlannedRoadmapWhat “planned” means

Components

  • DisclaimerNote: the scope statement, inside the orientation.
  • Field and ReadingInput: one measurement or one choice, not a form.
  • Button: continue, and a real "Skip for now".
  • Value and CareCard: the reader's own number, and a next step only if one is real.
  • EmptyState: the honest payoff when every input was skipped.
  • ConsentSheet: later, when a feature needs it.

Example

Viewport width
Theme
Accent theme
Accent

NOT IMPLEMENTED. The opsinjs component `onboarding-screen` does not exist in any released version of opsinjs. There is no package to install, no module to import and no props interface to generate code against. Everything on this page is a specification of intended behaviour and may change without notice. Do not write code against it.

onboarding-screen is not built yet

This frame will embed /view/base/base-lyra/screen/onboarding-screen?mode=light, which renders under the product theme rather than the documentation chrome. There is nothing at that address yet.

PlannedRoadmapWhat “planned” means

Phone · 390px · /view/base/base-lyra/screen/onboarding-screen?mode=light

The onboarding screen is still a specification, so its frame shows the not-built notice. The payoff step, which shows the reader's own number, is its only lifted surface.

Content

Spend the reader's attention on scope and the next step, not on features. "Understand your heart" is a description. "Improve your heart health" is a health claim, and a reader remembers a claim made at first run. No status colour appears, because first run has no clinical state to grade.

Accessibility

  • Each step has one heading, and focus moves to it on advance, never to the continue button.
  • Progress is stated in text, such as "Step 2 of 4", not by dots alone.
  • Back never destroys input (WCAG 2.2 SC 3.3.7), and no step has a time limit (SC 2.2.1).
  • Sign-in needs no memory test (SC 3.3.8), so pasting a one-time code must work.
  • Skip is a labelled, focusable control of at least 44pt that stays beside continue at 200% text.