[Products]
Products, with the status attached.
3 products, each built because we needed it rather than because a market validated it. We publish the status of each one honestly — including the parts that are not finished.
- MangofoldReact Native (Expo) · iOSLive
- FamilyFoldsFlutter · iOSIn development
- bottlemailNext.js 14 · WebRetired
[Rationale]
Why each one exists.
A product page is easy to write. This is the part that matters — why each of these exists and what problem it was built to solve.
Mangofold — for groups that outgrew a group chat
Real-time chat was never the hard part; losing the wiki, the calendar and the history was. Mangofold keeps all three inside one invite-only server, scoped to a group of twelve rather than a network of millions.
FamilyFolds — for households running on memory
Chores, points, rewards and the password drawer are the same recurring argument in different clothes. FamilyFolds models the loop once and makes the ledger server-authoritative, so nobody has to trust anybody's arithmetic.
bottlemail — for the thing you never sent
Addressing a bottle by email address instead of a name is what turns a party trick into a real inbox. The addressing design does the work: the server routes each letter to an inbox it cannot read.
[How we write about status]
Nothing ships quietly.
A product page that claims everything is finished is a product page you cannot trust. This is the convention we hold ourselves to.
Running in production with a reachable URL. If something is still missing it is listed on the page, not hidden.
Architecture and design are defined; the product is not usable. Pages describe the intent and separate it from what exists.
Taken offline but preserved. We document the reasoning and the architecture rather than quietly deleting the page.
Current: Mangofold (live) · FamilyFolds (in development) · bottlemail (retired)
[Contact]
Write to us.
Questions about a product, a bug report, or feedback — email is the fastest way to reach the studio, at c543e4@protonmail.com.