Content
@
0 reply
0 recast
0 reaction
christopher
@christopher
we are about two and a half weeks into the client build and the team has learned sooo much. 1. @neynar @privy, @dynamic and NextJS is good enough. 2. mobile/React Native is much harder due to separation of concerns in the backend. 3. you will need a website, anyways. 4. target 99.99% SLO. serverless setups will get you there. 5. do not cache or optimize early. Redis is expensive. 6. you must be feature complete before launching. 7. data is a deep, dark, expensive well. 8. do not follow boilerplates or tutorials. 9. deploy with a monorepo. do not use pnpm or bun. they are too early or have hidden blockers. 10. you will need to run Postgres eventually. 11. i still don’t know how Dockerfile builds works.. 12. frames are fun but will be a sidequest. 13. most of your days are spent waiting for builds to pass. 14. do not use prettier or eslint. use Biome. 15. it’s OK to rapidly push to main. 16. move fast!
20 replies
3 recasts
123 reactions
zoo
@zoo
in the context of 6. what do people mean by building in public?
1 reply
0 recast
1 reaction
christopher
@christopher
good question — you can build in public, but you don’t have to launch. start a brand, publish roadmaps, share designs! the most important thing is to launch at some viable feature parity with your peers and competitors. your product should be living and breathing. if it’s read only, ngmi. if it’s write with limited read, ngmi. imagine Twitter without smooth infinite scroll or TikTok without autoplaying buffered videos.
0 reply
0 recast
0 reaction
