I've done a similar app and this was basically the reason why I'm discontinuing the app. You didn't have a polished offline-first sync solution back in the days and my homemade sync code is a spaghetti soup.

Thanks! I strongly agree.

A local-first, offline-capable model turned out to be one of the best long-term decisions. It makes the app faster, more reliable, and usable in situations where connectivity is poor or nonexistent. Sync then becomes an enhancement, not a dependency.

It also changes how you design software: you optimize for resilience and data ownership instead of assuming a server is always there. I’m convinced more apps would benefit from this approach, especially for tools people rely on daily.

And people think you need to go to the jungle of Honduras to lose connectivity. It can happen literally anywhere, in a parking garage, next to trees in a park, in the desert. Intermittent in a shopping mall, the list goes on. Also, I like apps being resilient.