The clutter fix. Your brief: "when I tap inside of somebody's card, it desperately needs to be laid out better." The proposal makes three moves. One, the tag chips that sat under EVERY enjoys and avoids line fold away into a tiny gold count that opens on a tap, because those chip rows were most of the visual noise. Two, enjoys and avoids become one tight two-column read instead of two long stacks. Three, every line is just its words, no labels repeated. Tap the toggle to compare.
S
Sara
Known since 2012 · Last connected 3 weeks ago
Heads up (2)
Avoids
shellfish, allergic
AllergicfoodShellfish
red meat
Red Meatfood
Enjoys and avoids
Enjoys
white meat chicken and turkey
White Meatfood
vegetarian meals mostly
Vegetarianfood
horror movies, the scarier the better
HorrorMovies
Avoids
dairy when she can help it
dairyfood
alcohol
Alcohol
Every line carries a chip row. Ten lines is ten chip rows.
S
Sara
Known since 2012 · Last connected 3 weeks ago
Heads up (2)
★ avoids shellfish, allergic 2 tags
★ avoids red meat 2 tags
Enjoys and avoids
Enjoys
white meat chicken and turkey
White Meatfood
vegetarian meals mostly 2 tags
horror movies, the scarier the better 2 tags
Avoids
dairy when she can help it 2 tags
alcohol 1 tag
Tap "2 tags" on the first enjoys line: the chips unfold only when asked for. Tap a line's words to edit it, exactly as today.
Same information. Half the height. The words breathe.
At scale: Sara with 20 lines today is 20 chip rows, about five screens of scrolling. Proposed, 20 lines is one tight card about two screens tall, and no tag chip draws until a line is asked. Nothing is removed: search, lenses, and groups still read every tag exactly as now. This is display only, no database change.
The event card (your D23 dinner shape, loop 40). A hand-built group grows one details card people can read at a glance: drop in the deets, tick who is coming, and one button copies it all for the group text. It sits ABOVE the plans section that v2.17.0 just built, so one screen carries the whole event: details, plans, people.
D23 Dinner Group
6 people · plans live under D23
Event details
WhatDinner during D23
WhenFri Aug 15, 7:30 pm
WhereThe Fifth Rooftop, Anaheim
ParkingStructure on Clementine, paid
Menuthefifthoc.com/menu
NotesReso under Trish. Meet in the lobby.
Copy builds the message from the filled fields only. Empty fields never print.
Who is in
✓ Sara 📱
✓ Aurora 📱
Jay 📱
✓ Lynn no number
The tick is "coming"; the phone mark means a number is on their card, so the group text can reach them.
Plans for this group
Set up reservations Planned · Aug 6
Order snacks for road trip
Create packing list
This part is already live in v2.17.0. The event card stacks on top.
At scale: the details card is fixed height, six short rows at most, whatever the group size. The who-is-in list at 20 people is one screen of 44px rows, tick on the lift, scroll never ticks. Copy for group text is one tap from the top of the screen. Needs a small migration (event fields on groups plus a coming flag), which ships alone per the standards.
The packing list find, yours: "there's just no way to just make a little like ticked off simple list in here... now we're going to bump them out and expect them to go somewhere else. And that's kind of defeats the point." Proposal: any task can hold its own little tick items. Dictate the lot into one box; each line becomes a tick. The task row shows quiet progress.
On My Mind · Want to
Create packing list 3 of 8 packed
Tap the words to open the task, exactly as today. The little count and bar are the only new things on the row.
Create packing list
D23
The list
✓ears
✓chargers
✓water bottles
sunscreen
portable fan
trading pins
snacks for the room
autograph book
One dictation makes many items: it splits on commas and line breaks, so you talk the whole list in one breath. Tick anywhere on the row, on the lift, so scrolling never ticks. Ticking the LAST item offers to tick the task itself: "All packed. Done?"
At scale: a 30-item list is one screen and a half of 44px rows inside the open task only; the On My Mind list itself never grows, every task stays one row plus a hair of progress bar. The items live in their own little table so nothing about tasks changes shape. Small migration, ships alone.
Little details grouped by family. The same family headings v2.17.0 put in browse and clusters, now quietly organizing a person's Little details. A detail line whose tag sits in a family files under that family's heading; the rest keep a plain list at the bottom. Display only, nothing stored.
Little details
Disney
has been to every park opening since 2005
collects Haunted Mansion pins
Food
orders oat milk lattes, extra hot
Everything else
her mom is Mary
daughter turned five this year
drives the blue Bronco
At scale: 25 details across 4 families reads as 4 short labelled runs instead of one 25-row wall, and the ones with no family stay findable at the bottom, never hidden. Zero migration: it reads tags.family_id, which is already live.