Lessons from Building in Public
medium.com1 pointsby sampl1 comments
- Talking about who my customers are and what value I'm trying to create for them
- Designing the basic UX
- Interviewing potential users
- Running usability tests
- Designing a brand
- Maintaining a product backlog
- Reading documentation
- Writing code
- Fixing bugs
- Learning how to write unit tests
- Spending days trying to figure out Firestore security rules
- Prepping for a mini-launch (including writing this HN post)
- Getting stuck/bored/tired
- Making lots of mistakes
Next steps: - Sales
- More usability tests/interviews
- More features
- Improving the visual design
- Subscriptions with Stripe
Tech stack: - React + Create React App (with styled components)
- Firebase for the db (Firestore), plus Firebase auth and hosting
Like in any startup, there's a rollercoaster of ups and downs. The visual brand was designed in a couple hours, but figuring out how to finally secure the Firestore database took almost a week. There are moments where I'm having a blast, moments where I want to give up, and lots of hours where nothing much happens at all.
You send your tasks to [email protected], and it'll send you a todo list every morning. You can reply to complete, postpone etc.
The point is to not have a separate place for seeing and managing a giant database of todos. You only ever see what's relevant now, and in the place you already look for everything else (email).
1. https://dobbymail.com/