ShotNest · 2026
A connected treatment-management system for iPhone and Apple Watch
Making the next step unmistakable.
ShotNest brings dose timing, injection history, medication supply, side effects, progress, and learning into one coherent routine. I defined, designed, engineered, and prepared the product for release as one connected system.
Role
Founder & AI-Native Product Builder
Product strategy, discovery, architecture, interaction design, implementation, validation, and release planning.
Product scope
Onboarding, reminders, shot and symptom logging, medication supply, progress, learning, HealthKit, and Watch surfaces.
Technical foundation
Expo · React Native · TypeScript
Local-first storage · Apple HealthKit · Apple Watch
Product state
Working release foundation
Core product flows implemented, tested, and prepared for App Store submission.
01
Website · Product story
Make the routine feel understandable before asking for interest.
The redesigned website leads with the working product, then explains the difference it makes. Warmth earns attention, motion supplies proof, onboarding shows how the system becomes personal, and privacy appears before the early-access request.
Lead with the routine
The hero names the practical job first: see what is next, log the moment, and keep the surrounding details together.
Show change, not inventory
Each product story pairs a real flow with the user outcome, such as turning refill planning into a calm heads-up.
Make setup part of the promise
A four-step explorer shows how goals, medication, cadence, and privacy become a useful first plan.
Connect trust to action
No account, on-device processing, plain-language privacy, and a working early-access form create one coherent path.
01
The current public front door
The hero combines one direct promise, a live product moment, Pollito, privacy reassurance, and two clear paths: join early access or watch the product work.
Warm, not clinical
Cream, cool aqua, lavender, coral, rounded frames, and Pollito soften the first encounter without hiding the app’s focused dark interface.
Specific, not promotional
Real terminology, current screens, and task-level outcomes replace broad feature language with visible product capability.
Reassuring, not vague
Privacy and medical boundaries appear in direct language at the moment each becomes relevant.
Motion-led product proof
The redesign replaced selectable screenshots with product moments that explain themselves.
Why motion
A static interface can show hierarchy, but it cannot show how treatment history, supply, progress, learning, and dose goals unfold. Short simulator recordings make sequence, feedback, and depth visible without turning the page into a tutorial.
How the story stays focused
Each recording sits inside a dimensional phone with two compact callouts and one outcome statement. The surrounding composition does the interpretation so the recording can remain concise.
Working product evidence
The interface moves because the routine moves.
A simulator recording carries the visitor from history into a recent shot record. The surrounding callouts explain the value of the moment without interrupting the proof.
Native controls remain available. The poster stays still when reduced motion is preferred.
02
Capability paired with consequence
Next shot, supply, adding supply, progress, and medication dose goals each explain both what the product does and what becomes easier for the user.
Next shot
A glance replaces another date to remember.
Supply
A calm heads-up replaces a refill surprise.
Add supply
Important label details start verified.
Progress
Patterns replace pressure from one number.
Dose goal
Clinician-guided changes keep a clear history.
Onboarding as evidence
The setup flow proves that ShotNest becomes useful before the first summary appears.
The explorer moves through what matters, medication, shot rhythm, and a ready first plan. It uses the application’s real setup language and screens, making personalization, prescription handling, and on-device privacy visible as one connected system.
03
A real setup story
Four selectable steps share one device frame. Automatic rotation introduces the sequence, while pointer and keyboard input stop the timer and hand control to the visitor.
04
Swipeable on mobile
Cards become a horizontal snap track, the device remains the focal point, and a compact position indicator makes swiping discoverable.
05
Product first, outcome second
On narrow screens the recording appears before supporting copy, then the user outcome closes the story with the same hierarchy as desktop.
Automatic introduction
Rotation exposes the whole setup story without requiring a first click.
User control
Hover, focus, click, or tap stops rotation and preserves the chosen step.
Mobile gestures
Swipe, snap alignment, and visible pagination make the compact carousel legible.
Privacy in context
On-device prescription processing appears beside the medication step, not in a distant policy.
Delivery system
Motion, accessibility, conversion, and routing were treated as one release surface.
06
Support and privacy retain different emotional jobs
Learn stays close to the app’s dusk-purple environment. Privacy moves into a brighter cream and aqua composition so the promise is direct, plain, and easy to scan.
Progressive media loading
Recordings load near the viewport, pause out of view, warm after the critical path, and retain static posters as dependable fallbacks.
Accessible interaction
Keyboard tab behavior, focus trapping, focus return, reduced motion, mobile tap targets, swipe handling, and reveal-safe print output shape the interaction layer.
Working early access
The modal validates email input, submits to Loops, reports rate limits and failures, and presents a real success state without exposing form logic in the page shell.
Shared release surface
Homepage, support, privacy, navigation, footer, metadata, canonical redirects, robots, and sitemap ship through the same lightweight Vite and Sites build.
Outcome and status
A public product story that moves from understanding to a real early-access action.
Implemented
I designed and built the current ShotNest website across the homepage, support, privacy, navigation, footer, and deployment surface. It combines simulator recordings, a responsive onboarding explorer, outcome-led product stories, and a working Loops-backed early-access form.
Capability demonstrated
The site turns a complex treatment system into a sequence a visitor can inspect: what ShotNest changes, how it becomes personal, how sensitive information is handled, and what to do next.
Evidence boundary
The website and email collection path are implemented and publicly available. I do not claim waitlist conversion, acquisition performance, or market impact because verified outcome data is not yet available.
Next evaluation
The next review should measure promise comprehension, onboarding exploration, recording engagement, privacy understanding, modal completion, submission errors, and early-access conversion.
The website lets the product demonstrate its value before asking the visitor to join.
Visit ShotNestInterface gallery
The story explains the decisions. The gallery shows the breadth of the work.
Showing 7 of 18 views. Open any image to inspect it at full size.
Marketing Website · Motion-led introduction connecting the routine, product, Pollito, and privacy
Marketing Website · Four-step onboarding story built from the real setup flow
Marketing Website · Product recordings paired with the change each capability creates
Marketing Website · Practical learning and plain-language privacy as connected product stories
Marketing Website · Mobile promise, early access, privacy, product, and Pollito
Marketing Website · Swipeable onboarding preview with visible next-step affordance
Marketing Website · Product proof followed by the user outcome on a narrow screen
