02Independent concept studyAccessible mobile product

AccessFit

Helping prosthetic users notice patterns, remember changes, and arrive at appointments better prepared.

Role

Product framing, accessibility, safety UX, interaction design, prototyping

Focus

Daily self tracking, grounded summaries, clinician communication

Boundary

A communication aid that never diagnoses or replaces professional care

Today · 8:42 AM

A check in that respects your energy.

Six clear questions. Voice input when typing is difficult. No streaks, guilt, or hidden interpretation.

48 sectarget completion time

ACCESSFIT

How does your fit feel today?

2 of 6

YOUR WEEK

Comfort improved on lower activity days.

The opportunity

The most useful detail often disappears between appointments.

Fit, skin comfort, activity, and mobility can change from day to day. Remembering the timing and context weeks later is difficult, especially when the burden of documentation sits entirely on the person adapting to a device.

The design question was: How might a lightweight daily record help users spot patterns and communicate clearly, while protecting autonomy and staying far away from diagnosis?

Responsible starting point

Concept study · synthetic data
01

Listen first

Plan interviews with prosthetic users, prosthetists, and accessibility specialists before deciding which patterns are useful.

02

Reduce burden

Design for a check in under one minute, voice input, large controls, and a non visual alternative to the body map.

03

Keep the boundary

Separate observations, uncertainty, and questions. Never present an AI generated diagnosis or treatment instruction.

The flows show hypotheses to validate with users and clinicians. They do not claim medical efficacy and use synthetic entries throughout.

Product principles

Dignity shows up in the interaction details.

01

Low effort is a feature

One question per screen, optional voice notes, no forced typing, and the ability to stop and save at any time.

02

The user owns the narrative

Every summary statement can be edited or removed before it appears in a clinician report.

03

Urgency stays calm and direct

Severe or worsening entries trigger clear support options without alarmist language or a fake diagnosis.

04

Sharing expires

Users select the date range and content, set a time limit, and can revoke access from one place.

Interactive prototype

Complete a daily check in.

Choose a fit, select a comfort level, and mark an area. The summary changes using only the entries you provide.

AccessFitDaily check in · Step 1 of 3

SOCKET FIT

How does your fit feel right now?

Choose the closest answer. You can add context later.

A report designed for a conversation

User controlled · Time limited sharing
ACCESSFIT SUMMARY

Maya’s last 14 days

Prepared Sep 14
In Maya’s words

“I want to understand why late afternoons have been less comfortable.”

10 / 14check ins
4 daysfit changed
Afternoonmost noted time

Observed pattern

On four higher activity days, Maya recorded tighter fit and more discomfort after 3 PM. This is an association in the entries, not a confirmed cause.

Questions Maya selected

  • Could activity or time of day affect this change?
  • What signs should I track before our next visit?

Before sharing

You can revoke the link at any time.

Safety and limitations

The product must know what it should never do.

No diagnosis. Summaries restate patterns in user entries and name uncertainty.

No invisible sharing. Reports require explicit content selection, review, and consent.

No engagement pressure. Missing a check in never breaks a streak or triggers guilt.

No visual dependency. Every chart and body map has an equivalent text interaction.

No vague urgent state. Concerning entries lead to clear professional or emergency support guidance.

Build brief

Build with the safety boundary included.

The full prompt covers the product flows, AI grounding, accessibility, privacy, edge cases, and success criteria.

Build a mobile first responsive application called AccessFit for adults adapting to a prosthetic device. It helps a user record comfort, fit, skin observations, activity, and mobility, recognize patterns, and prepare a concise clinician report. It is a self tracking and communication tool. It must never diagnose, prescribe, or replace professional care.

Core flows: accessible onboarding; a daily check in under 60 seconds; a visual and text based body map; trends that do not imply causation; an AI summary grounded only in user entries; a user editable clinician report; time limited sharing and revocation; privacy controls; calm urgent support guidance.

Use bone white, deep navy, soft blue, warm amber, and restrained red only for urgency. Avoid clinical stock photography, glowing AI effects, gamified streaks, and decorative dashboards. Prefer large type, clear steps, and strong hierarchy.

Separate observations, uncertainty, and questions for a clinician. Cite the exact entries supporting each statement. Let the user edit or remove every statement. Log consent and sharing. Keep a visible statement that AccessFit is not medical advice.

Support keyboard and screen readers, large text, high contrast, voice input, reduced motion, a non visual body map alternative, 44 pixel targets, no forced time limits, and simple language.

Use typed entities for User, DeviceProfile, AccessibilityPreference, DailyCheckIn, BodyRegion, SymptomObservation, ActivityEntry, WearSession, Trend, SummaryStatement, EvidenceReference, ClinicianReport, ShareGrant, ConsentRecord, and SafetyEscalation. Build a progressive web application with offline drafts, synthetic data, accessible chart tables, and a mocked grounded summary service.

Measure check in time, completion consistency, summary edits, report completion, share revocation, accessibility task completion, and appointment preparedness. Never optimize for time spent in the app.
Download both prompts