0 / 0 pages shipped · hover a tile
Every page, designed then built
A static site that uploads anywhere, five demos that run in the browser and send nothing, nine app screens on a design canvas and a character set ready for the real app.
Mission debrief · 01 / 03
kip
kip turns the rotation of people raising a newborn into one team: parents, grandparents, nannies and night doulas share one log, every entry signed with a face, so no detail is lost between shifts.
/briefing
The objective
Babies aren’t raised by one tired parent. They’re raised by a rotation: two parents, a grandparent, a nanny, a night doula. Baby trackers tend to assume one person holding the phone; kip is built for the rotation. Every feed, nap, diaper and dose lands in one shared log with the face of whoever logged it, a handoff card briefs the next person before they ask, roles give each person exactly what they need, and plain-sentence patterns go to the parents, never diagnoses. The ambition: nothing dropped between shifts, no dose given twice by accident, and checkups that start with real data instead of guesses. It’s a [[Test flight]], a concept with no app yet, so the site lets you try it as any of the five people in June’s day.
Eleven pages and a real 404, coded by hand after ideation and wireframes, with no framework. A GSAP-scrubbed ribbon follows one day through four handoffs, a Try it page runs the shared log in memory (switching people is a handoff, and vitamin D asks before a second dose), a role builder redraws each person's phone, and a pediatrician report rebuilds across three ranges and prints only the paper. Dark mode is one token swap, Command-K search covers every page, every page reads without JavaScript, and motion rests under [[Reduced motion]].
Mission parameters
/systems · 6 deployed
Systems deployed
Open a system to see what it does, why it matters and, in Engineer mode, how it works.
SYS-01
A day on one ribbon
GSAP · scroll
What it does
Scroll the home page and June’s Tuesday slides past a fixed “now” line, from 6am to after 3am. The sky changes with the hour, entries land, and each handoff card lights up as the next person takes over.
Why it matters
“Everyone in one place” is easy to say. Watching five people pass one day between them, without anything getting lost, shows it.
Under the hood
One table of shifts, entries and chapters draws both the static ribbon and the scrubbed one, so the no-JS and [[Reduced motion]] versions can’t drift from the animated one. A GSAP ScrollTrigger scrubs a single number, the minute of the day, and one render function moves the ribbon, blends the sky and updates the count.
Curious how it works?
Switch Crew level to Engineer for the technical breakdown.
SYS-01
Try it, as anyone
In-memory demo
What it does
Be Ari, Sam, Nana, Rosa or Jo. Log a bottle or a nap and the log, the handoff card and the pattern note all update. Switch people and kip tells the new person what they missed.
Why it matters
There’s no app to download, so the site has to let you use it. Trying it as the grandparent, not the parent, is what makes the roles make sense.
Under the hood
A small in-memory simulation: switching people is a handoff, the med button checks who already gave vitamin D today and asks before logging another, and the pattern note changes only when the log does. Nothing is stored; reloading starts the afternoon over.
Curious how it works?
Switch Crew level to Engineer for the technical breakdown.
SYS-01
Roles you can see
Permissions · a11y
What it does
Flip what Nana and Rosa can do, and their two phones redraw beside the switches: turn off meds and Nana’s med row says it’s hidden.
Why it matters
A permissions table is hard to picture. A phone that changes when you flip a switch isn’t.
Under the hood
Each switch is a real switch control that redraws that person’s phone. Turning off logging turns off meds too, and turning on meds turns logging back on, so the permissions can’t contradict each other. Pattern alerts are locked to parents here and on the insights page, so the two pages agree.
Curious how it works?
Switch Crew level to Engineer for the technical breakdown.
SYS-01
A report that prints
Report · print · CSV
What it does
Pick a range and what to include, and the pediatrician report rebuilds: the bars grow to their new heights, the averages change, and it prints as a clean page.
Why it matters
Checkups shouldn’t start with a parent scrolling their phone and guessing. And a report is only useful if it looks like a document, not an app screen.
Under the hood
Three ranges with real rebuilds: when the bar count stays the same, each bar eases to its new height; when it changes, the bars redraw and grow in. Unticking every category shows an empty state, a print stylesheet prints only the paper, the sample CSV is built in the browser, and the share link says it’s simulated. Medication rows say “as directed”, never a dose.
Curious how it works?
Switch Crew level to Engineer for the technical breakdown.
SYS-01
Patterns, not diagnoses
Copy · alerts
What it does
Log a few bottles close together and kip says so in a plain sentence. It says what changed, never why, and the note only goes to the parents.
Why it matters
Parents want to notice a change early without an app scaring them. kip spots patterns; the pediatrician decides what they mean.
Under the hood
The pattern note is picked by what was just logged against June’s usual afternoon, and every version describes the change without naming a cause. Switch to anyone who isn’t a parent and the page says they wouldn’t get the note.
Curious how it works?
Switch Crew level to Engineer for the technical breakdown.
SYS-01
The village, drawn
SVG · characters
What it does
Six characters, each a different shape as well as a color. You can tell who logged a feed by silhouette alone.
Why it matters
Attribution only works if it reads in half a second, half asleep.
Under the hood
Each character is one [[SVG]] symbol in a shared sprite, so the same source draws the 40px avatar on every log entry and the full-size figures on the home page. Shape carries identity; color is backup, which also keeps it readable for color-blind parents.
Curious how it works?
Switch Crew level to Engineer for the technical breakdown.
/impact · 5 problems solved
Problems solved
What the site does for the people who run it and the people who visit it.
SOLVED-01For visitors
One log instead of a group chat
Before
With five people caring for one baby, the group chat becomes the log, and nobody trusts it.
Now
One shared log where every feed, nap and diaper carries the face and name of whoever logged it.
Result
“Did she eat?” gets answered by opening the app, not by texting everyone.
Under the hood
Every entry has one shape (who, what, when), so the log, the handoff card and the counts read from the same list and can’t disagree.
SOLVED-01For visitors
Shift changes without lost details
Before
Every shift change loses something: the last feed time, the nap that ran long, the note about the rash.
Now
A handoff card when someone takes over, with everything since they last had the phone and who did it.
Result
The next person starts caught up, without a phone call or a note on the fridge.
Under the hood
In Try it, switching people is the handoff: the card lists what others logged since that person’s last entry.
SOLVED-01For visitors
No double doses
Before
Two caregivers each give the morning vitamin D, because neither knew the other already had.
Now
Before logging a med, kip shows who already logged it today and asks before logging another.
Result
A second dose takes a deliberate “log it anyway”, not a habit.
Under the hood
The med button looks for today’s earlier dose before it logs. Roles that can’t log meds get the button switched off, with the reason.
SOLVED-01For visitors
Share what each person needs
Before
Most baby apps share everything with everyone, or nothing at all.
Now
Roles plus per-person switches, with each person’s phone redrawing as you flip them.
Result
Nana can log feeds without seeing the med history, and pattern alerts stay with the parents.
Under the hood
Logging and meds are linked, so no switch combination can contradict another.
SOLVED-01For visitors
A concept that doesn’t pretend
Before
A concept site dressed up as an app-store listing, with badges and stars, promises an app that doesn’t exist.
Now
No badges, reviews or users. Every call to action is “Try it” or an early-access form that says it sends nothing.
Result
The site can be shown to anyone without a caveat, because it never claims more than it is.
Under the hood
The early-access inputs have no name attributes, so even a submit without JavaScript carries nothing anywhere.
/manifest · what shipped
Mission manifest
Everything this mission delivered, planned and mocked up first, then built from the ground up.
Mission · planet
Role
Designer + developer
Platform · Year
CMS collections
0 collections
Mission type
0 disciplines
Drag the tags
Mission parameters
All met
Status
Live
Self-initiated identity
/telemetry
By the numbers
12
pages, including the 404
5
interactive demos you can try
0
bytes sent by any demo or form
0
app-store badges, reviews, ratings or press logos
/stack · 0 tools
Tools in orbit
Every tool this mission ran on. Pull one out of orbit and let go; it finds its way back.
Hover a tool
Tools in orbit
/observatory · from this mission