Stressie · iOS · 2026 · metrics being validated
01Overview
Stressie is a workplace wellness app. V2 got people to check in and use quick resets, and its pilots ran with Amazon's hardware team, InKind and 50 Austin PD officers. V4 is what comes after the check-in, and I designed it in Figma and wrote it in SwiftUI myself.
Outcomes
NoteUsage metrics are being validated now. D30 retention and off-work opens go here when they land. The bar is V2's 17.4%.
02The problem
Retention went from about 2% to 17.4% and daily engagement from 12% to 56%, on quick resets and a calm screen. The same pilots said trust was asked for too early, the points had no value, and the app went quiet after work. Meanwhile wellness moved into the room: run clubs, sound baths, dinners on Luma and Partiful.

"I haven't built trust with the app yet, so sharing personal feelings this early is uncomfortable."Pilot participant, Amazon hardware team
"I didn't find the coping points compelling as an incentive. I don't know their value."Pilot participant, InKind
V2's first screen asked for five minutes of questions before the app had done anything for you.
03At Work
You slide to answer and the shape changes with you. Releasing the slider saves the check-in and opens a panel with two short films, two quick resets and a way to talk. Finishing a reset earns coins on the spot.



Check in, the panel, the coin. Seven shape levels run orange to violet, never red.
Decision
The release gesture is the commit. There is no Continue button, so the panel opens on the same drag.
Cut
The 0 to 10 score. The shape names the feeling, running hot, and never grades it.
04Off Work
Partner venues and public places get different pins. Chips filter for open now, spas, parks and movement. Every place shows a real offer with a price in coins, and a redeemed offer becomes a code for the front desk.



The location prompt, the map, the code you show at the desk.
Decision
The first check-in happens before there is an account, and location is requested by the map, not the onboarding.
Cut
Permission screens on day one. V2 asked for everything up front, and the pilots told us it cost trust.
05Community
Events live on the same map: breathwork circles, pottery socials, dinner nights, a quiet hour online. Reserving costs coins. Hosting is name, description, time, capacity, in person or online, free or paid, then a preview of exactly what guests will see.






Decision
Online events publish instantly. In-person events wait for a human to approve the address.
Cut
Free seats. A seat paid for with a week of check-ins gets used; a free one gets skipped.
06Coins
Five coins per check-in, up to three a day, more for a finished reset, 200 for a friend who checks in. Short of a reward, you top up. Coins leave only through a button that names the price. The coin itself took four rejected rounds, an opal gem, an agate coin, a wreath and a honey centre, before this one: gold, three raised petals, rendered once from one scene.



The first coins arrive before the account. Rewards. The invite flow, the one screen with its own colour.
Decision
"Redeem for 80 coins", never "Continue". The price is on the button, every time.
Cut
Streaks and confetti. The reward is two beats: the coin settles, then the words. Nothing shouts.
07Designed and built
The event page, Figma render and simulator build, measured against each other at 3 px/pt.
What building it changed, 1
The reward haptic fires from the coin's completion handler, on the visual landing. In Figma it was a note. In code it became the timing.
What building it changed, 2
The design system lives in code, and a lint fails the build if a screen names a colour, radius or type size. That rule exists because I was writing both.
What I built: every screen and flow, the design system and its lint, check-in, resets, the map, community, coins, referral, Talk's voice UI, three languages, Reduce Motion and Dynamic Type. What I did not build: the backend, payments and the model behind Talk. Those run on local stores with the seams marked for the team.
The call I owned
The founders wanted every event live instantly. I held the line on in-person events because a stranger's address needs a human check before Stressie puts its name beside it. The cost is real: a host waits, and some will not come back. Whether I was right is one of the things being measured now.
08Reflection
Put a person behind the approval queue first.
Right now the queue is a state, not a reviewer. The first in-person host will find that out.
Ship the sink with the coin.
I shipped earning before redemptions were live. An economy with no exit is just points again.
Get a second engineer in early.
Working alone was fast. The numbers should not be trusted until someone else has read the code.
Designed and built by Bhanu Kowshik · stressieapp.com ↗