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
122 reactions
Jacob
@jrf
are you sure about 6?
1 reply
0 recast
0 reaction
christopher
@christopher
yes, your highest affinity users will churn within a month if you do not have mandatory features (notifications, emails, seamless read/write)
2 replies
0 recast
1 reaction
Jacob
@jrf
gotcha, mandatory is different than feature complete in my mind, maybe i misunderstood
1 reply
0 recast
2 reactions
christopher
@christopher
i’m going by this, feature complete is a subset of an alpha release (i.e. we must ship mandatory products that are feature complete): https://en.wikipedia.org/wiki/Software_release_life_cycle
1 reply
0 recast
0 reaction
Jacob
@jrf
ah gotcha, i see there's a definition i wonder if "all planned" features is too much if the overwhelming majority of product insights occur post-launch
1 reply
0 recast
1 reaction
