Build notes
- How we caught ourselves overpromising
Before we publish a promise, we check it against how the product is built. Five times the words said more than the design, and what we changed.
- Invites with a blindly certified code: how they will work
The inviter's device will create the invite code, and our server will certify it blindly, without seeing it. What will stay visible, and what it will cost us.
- Subject lines and recipients are content too
Who writes to whom, and about what, is part of the email. Why we will store subject lines and addresses encrypted, and what that will cost.
- The first rows of the inventory are printed
We promised to publish the inventory before launch. What is printed already, what is still printing, and how it will change.
- Where your password goes when you sign in
How password sign-in will work: what the server will see, what a leak of our database would give, and what it will cost us.
- Why we start with the inventory
Before there is a product, we decided what we will keep about people and publish it as a four-part list. Why we do it this way, and what it costs us.