A place for developers to talk about building on Farcaster.

/dev

More things I’ll say on farcaster but not on X: I’ve gone sour on NextJS and have been looking for alternatives. Tan stack start from the author of react query looks early but promising. A great review of it and how it compares to nextjs can be found here https://youtu.be/Iun1DE_oHG0?si=EwNPNa3Hxb8RqdTO

Something I would add to the Next conversation: it’s ok to use Next. 

Personally Next has allowed me to ship ideas fast. Over the last year I’ve shipped around fully 10+ fully functional marketing apps for Pinata on Next, including @candyroad, @photocast, and Snippets.so. That doesn’t include the frames, which would be in the dozens. These are apps that if we had to scale them into full products, it wouldn’t be that hard to move to a more robust full stack. 

The key is I didn’t over analyze and build with the goal of supporting 10k users. I built with the purpose testing an idea and providing an example. Depending on your position you may value optimizing for growth more, but I think generally it’s agreed to ship fast first. There’s no point in wasting time on an idea that might suck.

If you genuinely don’t like DX that’s fine too. Build with the framework that makes you excited to code. 

Whatever the case may be, just ship it.

https://photocaster.xyz| Upload high resolution photos to Farcaster

https://candyroad.cloud | Sell your content in frame

DX Engineer | Head of Developer Relations at /pinata | Tinkering with everything | stevedylan.dev/links

I am still surprised Next took off for web3 use cases which are client-focused. Much of Next’s SSR magic isn’t really applicable if your client needs to respond to wallets.