A place for developers to talk about building on Farcaster.

/dev

There's no way an app will be fast enough without keeping most state local.
Having a proper sync engine and local state isn't trivial but once it's setup you can reduce a lot of the issues that come with fetching and caching since the sync engine ensures that your app has the data and it's up to date.

There's no way an app will be fast enough without keeping most state local.
Having a proper sync engine and local state isn't trivial but once it's setup you can reduce a lot of the issues that come with fetching and caching since the sync engine ensures that your app has the data and it's up to date.

https://x.com/karrisaarinen/status/1834463400975544778

The open web is dead, long live the open web. ⌐◨-◨

Building /warpcast and /farcaster

— gabrielayuso.com

Developer 🤓 build, develop and operate Farcaster solutions @ dtech.vision also love tech, decentralization, fitness and oldschool rap 😎

I've done "local first" on native, not on web yet.
It's possible to do local first with 3p APIs you just need to write a custom way to continuously call the APIs and merge the results with the data you have locally.
That's basically what I did with Tumblr APIs back in the day.
You could also just integrate the 3p API on your backend and not your client, if possible.

Have you played around with local first sync?

one thing I am yet to figure out is how to show the few parts one has 3rd party APIs in a way that's pleasant if the rest is so fast.

Launching Farcaster community client for Nouns soon @tenfold
Past: AI and crypto rubinovitz.com

No.
There is a touch of persistence but we mostly rely on React Query. I'm just getting more familiarized with that part of the app. I've mostly been doing backend, Redis and UX stuff so far.

Part of why I’m (cautiously) excited about projects like https://electric-sql.com

Needs more time to bake, but promising!

I agree, relying entirely on server state for an ondevice app is dooming your users to network latency hell. Using local state with a sync engine is a no-brainer if you want a snappy experience while maintaining data integrity.