Fall Prevention

Falls are one of the biggest health risks for older adults and people with cognitive impairments: severe injuries, lost independence, rising care costs. Most existing products are reactive, built around emergency alerts and post-fall intervention. Almost none address the behavioral side, and adherence to prevention strategies stays low because nothing keeps people motivated or engaged.

The app operationalizes Dr. Kemp's research on MCII, mental contrasting with implementation intentions. Users set a meaningful goal, visualize the outcome against the obstacles in their way, then build if-then plans for each obstacle. The app walks clinicians and patients through that intervention and carries it home with behavior tracking, supportive notifications, and progress monitoring.

With a working build due in front of the client, I learned Swift, SwiftUI, and Firebase in weeks, implemented the client's UI feedback (positive-reinforcement wording, accessible color, clearer icons), and led the deployment to TestFlight.

I ran the product side too: milestones, product backlog, requirements, and the communication line between the client, stakeholders, and the team.

With the MVP out, I ran a heuristic evaluation and collected structured user feedback. Five themes came back consistently: navigation, data visualization, the goal-setting flow, missing functionality, and visual design.

The feedback was clear enough that patching wasn't the answer. I started the revamp from the information architecture: a new user flow first, so every later screen decision had something to hang on.

The project had no design system, and it needed one more than most: a web portal was being built in parallel by a second team, and clinicians would move between both. I built the shared system, type, color, and components, so the app and portal read as one product.

Each pain point from testing got a direct answer. The pie chart that made users feel judged became progress visualization that motivates; the goals page now separates daily from weekly progress; goal detail screens restate the MCII plan behind each goal so users keep their original motivation in view; and the eight-page goal-creation flow was collapsed and made editable without starting over. Per the client's request, streaks and badges made consistency something to keep rather than something to remember.

That redesign is what produced the numbers at the top: half the time on task, 95% completion.

Wearing multiple hats

Designer, iOS developer, and PM in one project. On a lean team, spanning all three made me the person who could see the product, the code, and the client at once.

UX debt becomes backend debt

The deepest usability problems needed backend changes we couldn't make without delaying the release. Design decisions made early in a project compound, in usability and in timeline.

Ship, then iterate honestly

The MVP met the client's immediate need; the research it enabled is what justified and shaped the redesign. Prioritization is the product skill I use most from this project.