01 / FLAGSHIP CASE STUDY · INDEPENDENT PRODUCT
Support for the next moment.
A native iOS experience for starting everyday activities, finding sensory space, and returning after interruptions.
Support that makes room
for the person.
01 / THE 30-SECOND READ
Naming a task, choosing a priority, estimating time, and remembering where you stopped are separate demands. NeuroMode asks whether support can be useful before someone has the energy to organize all of them.
THE DESIGN QUESTION
How might support make the next action manageable without making setup, sensory demands, or recovery another task?
The dates identify repository milestones and the case-study audit, not an end-to-end project duration. This is everyday support, not a diagnostic or treatment product.
02 / RESEARCH & FRAMING
The product existed before this formal case-study reconstruction. Desk research, comparative documentation review, and a source-based heuristic walkthrough explain and challenge the implementation retrospectively. They are not presented as the historical cause of every decision.
Evidence base: SwiftUI behavior, retained screenshots, two Git milestones, and validation records. No completed interviews, surveys, or participant usability sessions were found.
Lists, sections, and subtasks
Externalize and organize work.
A visual day timeline
Place activities in time.
Focused everyday tools
Choose a tool and judge its output.
NeuroMode’s opportunity is a short route from a present need to an adjustable action. Local task templates favor predictable behavior over broad interpretation. The cost is limited suggestions that may not fit someone’s activity.
Comparison scope: official product descriptions reviewed for the case study; no hands-on benchmark or competitor accessibility audit.
These are conceptual behavioral lenses and constructed scenarios, not validated audience segments or participant quotes.
The supplied September 25 research dossier uses these sources as design lenses, not proof of NeuroMode’s effectiveness.
03 / INFORMATION ARCHITECTURE
Today offers immediate support; the other destinations organize deeper capabilities. Each tab has its own native navigation stack. Less stimulation replaces the tab shell with a quieter experience—it is not a sixth destination.
Trade-off: shared destinations are easier to reach from several contexts, but Modes and Support may be difficult to distinguish. A tree test should challenge that grouping.
Today → Help me start. Name an activity only when needed.
Make it smaller, choose a different step, or write your own.
Carry the activity and current step into a timed or untimed session.
Write the next action. Save it and preserve remaining time.
Open the saved session, read the cue, and resume deliberately.
Preserving context is an interaction requirement, not just a persistence feature.
Constructed walkthrough of implemented behavior. A failed save keeps the focus sheet open; a return does not silently restart the paused timer.
04 / REVERSE-ENGINEERED WIREFRAMES
Reconstruction turns a working interface into something that can be questioned: what deserves attention, what can wait, and what must survive a change in state?
The wireframes were created after implementation. They are not original discovery sketches. The Figma specification is complete as a handoff document; a live Figma file and evaluated Figma prototype are not yet available.
Today introduces a need before an inventory. Next Step elevates one action above a whole plan. Focus keeps the next step near the save controls. Quiet Room moves optional stimulation behind disclosure.
Reducing visible content can also reduce discoverability. The next evaluation should test whether people can locate secondary actions and exits, not assume that fewer elements mean less effort.
PROPOSED FIGMA COMPONENT
Preserve the activity, user-written next step, and paused state.
IMPLEMENTATION REFERENCE
Saving and pausing are one action. Close the sheet only when the save succeeds.
The handoff specifies semantic color modes, Auto Layout recipes, native text styles, component variants, error states, and a start-and-return prototype path. Those contracts make future Figma refinement traceable to actual product behavior.
Download the Figma build specification05 / EXPLORATION & TRADE-OFFS
01 / DESIGN DECISION
A full tool catalog exposes everything; a required check-in asks for explanation before help.
02 / DESIGN DECISION
An always-visible countdown may add pressure; removing time entirely reduces choice.
03 / DESIGN DECISION
Automatic adaptation risks surprise; one global quiet switch bundles different needs.
Alternatives are retrospective design explorations. They are not undocumented historical prototypes or proven winners.
06 / VISUAL & INTERACTION SYSTEM
Warm neutral surfaces and sage actions establish the product’s identity. Semantic typography and native controls keep that identity responsive to appearance, text size, and familiar platform behavior.
Color values are rounded source mappings. Increased contrast uses system surfaces; the custom accent has no separate increased-contrast asset. This is not a whole-app contrast or conformance claim.
07 / THE IMPLEMENTED EXPERIENCE
START / IMMEDIATE SUPPORT
Today gives starting, focus, and less stimulation clear entry points. At accessibility text sizes, useful actions take priority over the greeting.
Retained dark-appearance capture. Selected simulator states were reviewed; the complete accessibility matrix remains open.
PAUSE / SENSORY SPACE
Quiet Room starts silent. Breathing, animation, and audio are separate opt-ins. Back and Finish stay visible while optional comforts remain collapsed.
The unresolved question is whether Finish creates an unnecessary extra exit step. A calm visual does not settle that interaction question.
COMMUNICATE / CHOSEN DISCLOSURE
Support cards let people choose statements, add their own wording, and preview what will be shared. The design makes disclosure an explicit action, rather than treating personal needs as profile metadata.
Local-first storage removes account setup, but places responsibility on recovery. Backup validates a file before previewing replacement. Confirmation makes clear that restoration replaces current records and clears scheduled notifications and Live Activities; it does not merge them.
08 / EVALUATION & ITERATION
Repository differences and recorded integration testing show concrete changes. None of these revisions is attributed to participant feedback.
Git comparison eab8750 → ba80bcf. User benefit remains inferred.
Documented defect and fix in the validation report; no separate before screenshot retained.
Recorded revision and retained dark screenshot. No invented before image.
The project’s latest validation record combines final runs; it is not one uninterrupted all-green run. Tests establish technical behavior, not participant usefulness or release readiness.
Read the validation recordSeveral onboarding answers are stored but do not feed recommendation rules. Asking those questions creates an expectation that the answers matter. The next revision should either clarify that promise or connect it to tested behavior.
Other review priorities include preserving scripts and routine drafts after save failures, clarifying search scope, and testing whether recovery remains findable when optional prompts are disabled.
This independent project has no documented formal team or stakeholder workshops. Cross-functional thinking appears in the handoff: what persists, what remains a draft, when a save sheet closes, and what happens when permissions are refused. SwiftUI, SwiftData, Xcode, SF Symbols, XCTest/XCUITest, and Git are evidenced tools. Figma is the specified next design environment.
09 / OUTCOME & REFLECTION
NeuroMode demonstrates implemented support paths, reversible preferences, local recovery, and a design model that can be inspected beyond the screens.
A feasible native foundation: editable steps, preserved context, independent sensory choices, and documented technical iterations. Reverse engineering makes the architecture and its trade-offs explicit.
Run the prepared formative study, evaluate Figma refinements, and complete human assistive-technology and physical-device checks. Test mismatched suggestions and interruption recovery before adding features.
The assumption most worth challenging is that fewer visible elements always mean less effort. A simpler layout hides context; a hidden countdown hides time; a quiet room hides options. Each reduction creates a responsibility to preserve discovery and an exit.
The strongest next outcome would be a person finding useful support, understanding what changed, and returning with enough context to continue.
No clinical benefit, adoption, retention, or measured cognitive-load improvement is claimed. Participant research and a completed Figma prototype remain future work.
Less debating.
More together.
