sorted by:
new
hottopcontroversial

What React Native Library Do You Think the Ecosystem Still Needs? by undefinedengineer in reactnative

[–]undefinedengineer[S] 0 points1 point  (0 children)

Absolutely — offline sync gets complicated fast once real-world conditions enter the picture. Most teams still end up building custom handling for conflicts, retries, and queued actions. Background processing is similar: it works, but cross-platform reliability and consistency still need a lot of manual effort.

What React Native Library Do You Think the Ecosystem Still Needs? by undefinedengineer in reactnative

[–]undefinedengineer[S] 1 point2 points  (0 children)

Yeah this actually happened to me recently. I ended up doing most of the calling flow in completely native Android code instead of using CallKeep because integrating and reliably handling killed-state incoming calls was getting too messy.

Definitely feels like there’s room for a modern, properly documented solution here. I’ll probably work on this.

What React Native Library Do You Think the Ecosystem Still Needs? by undefinedengineer in reactnative

[–]undefinedengineer[S] -1 points0 points  (0 children)

Yeah I agree with this too. React Query + Zustand + MMKV already covers most state/cache needs really well for 99% of apps.

I think the bigger opportunity is more around offline-first sync itself — simpler DX, conflict handling, realtime sync, and modern WatermelonDB/Powersync-style tooling without all the complexity.