Self-initiated group coordination product
Selfso
A full-stack product for helping informal groups move from talk to shared memory to next steps without losing the thread.
Selfso is about helping people take action together.
People want to help. Someone has an idea, someone offers to bring something, someone writes a note, someone picks up the next move. For a while, everything is alive and moving.
Then things get fuzzy. The first idea is in a chat. The plan is in a note. A file is somewhere else. Someone joins late. One person slowly becomes the human database for the whole group.

Selfso
Product
Group momentum
Talk into action.
Selfso is about helping people take action together. Talk, pages, actions, files, stream, and Return stay close enough that a group can keep moving.
Product surfaces
The actual product is the point.
Chat, pages, and actions are not separate pitch slides. They are the same account, the same garden story, and the same shared space seen from desktop, mobile, and overlay states.
Homepage card
The quickest read of the product.
One mobile surface showing the action stack, controls, navigation, and the kind of living product state Selfso is built around.

Chat
Where the messy thing starts.
Talk stays close to the pages and actions it creates.



Pages
Where useful bits land.
Plans, references, and decisions get a place without leaving the group.



Actions
Where the next move keeps its reason.
Owner, status, timing, and source context stay together.



Brand world
The brand has a body.
Not just a logo and some colors. A little world I can keep pulling from when the product needs a mood.
01 / 06
Marks
The name gets a few jobs.
Wordmark, symbol, lockup. Boring words. Useful things when the page needs to stop explaining itself.
01 / 10
Threads
And then it softens.
Because Selfso is about people doing things together. It cannot only be red and serious.
01 / 07
From the homepage
A real shared thing.
The current Selfso homepage is built around one vegetable-garden story. The case study now breaks that one story into the product surfaces that matter: chat, pages, and actions.
Chat
Where it starts.
The group starts in conversation: small updates, decisions, worries, and offers. The UI needs to feel alive without forcing structure too early.
Mia
2 min ago
we have twelve tomato seedlings
Can someone take half before they outgrow the tray?
Sam
Just now
changed my mind on herbs
Mint needs its own pot or it will take over everything.
Lena
5 min ago
the south bed gets shade after four
Maybe peppers go in the raised box instead?
Ava
8 min ago
I can bring labels
But someone else needs to write them. My handwriting is chaos.
Noah
11 min ago
who has the hose connector?
The old one leaks by the tap.
Pages
What gets kept.
Useful details land in pages when the group needs shared memory: a plan, a rota, a seed list, and the open questions people keep returning to.
Page
Vegetable garden
Sunny bed is 3 x 5m. Keep tomatoes near the fence.
Compost first, then plant the seedlings
Page
Water rota
Morning check if it is hot.
Skip if it rained overnight.
Page
Seed list
Tomatoes, basil, chard, beans
Shared supplier sheet
Page
Open questions
Can beans climb the old fence?
Two compost bags or three?
Actions
What moves next.
Actions are the commitment layer. Each row keeps owner, timing, status, and source context close enough that the next move stays understandable.
Tomorrow / Kai
Borrow wheelbarrow
Soil prep / Jo
Pick up compost
Friday / Ava
Mark the beds
Today / Mia
Ask bakery for crates
Sat / Lena
Confirm Saturday crew
Connected memory is the product idea.
Most tools split group coordination into separate places: chat for talking, docs for notes, task tools for next steps, drives for files, and notifications for whatever is screaming the loudest.
Selfso tries to hold those surfaces together around the actual life of a group, so people can move from talk to notes to next steps without losing the thread.
One story, three surfaces.
The point is not to show a dashboard. It is to show how the same messy group effort can move from chat to memory to action without losing its thread.
The fuzzy part is not bad. It usually means something is happening. Messy, but alive. Classic humans.

Return
Catch up without starting over.
Mia added a harvest photo
Noor updated the garden plan
Sam accepted the next move
Water beds before noon
Motion capture
The product has to move.
These captures keep the garden-club story, action center, media overlay, mobile surfaces, and login brand motion tied to real product states.
More captures
The rest of the slate: channel-card studies, action-center details, the image overlay, and login brand-motion variants.
Calm but alive. Useful without becoming managerial.
I created the full brand world around Selfso: the name, positioning, copy, visual language, interface direction, animation system, product metaphors, homepage, onboarding ideas, and the whole feeling of the thing.
The homepage uses a garden club example because that is exactly the kind of world Selfso is for: a small room, a shared effort, and a fuzzy plan becoming real through people helping.
Full-stack product
A lot of machinery.
The machinery serves the product belief: realtime because groups move, read state because catching up should help, permissions because trust matters, and event history because memory should be recoverable.
React Router web app
FastAPI backend
PostgreSQL model
Realtime WebSocket layer
Native iOS app
Files and permissions
Read state and event history
Search, digests, tests, and runbooks
Good things take shape in motion.
Selfso is not another productivity platform. It is a personal attempt to rethink how informal groups keep momentum, and how small meaningful things can stay alive long enough to become real.


















