Question: 1/50
A mobile app must support offline usage and later synchronize changes when connectivity returns. Which architecture approach best fits this requirement?
Use a local persistent store and a sync layer with conflict resolution
Disable features when offline and require the user to reconnect
Rely only on in-memory caching for offline access
Store all offline changes in UI components until the next launch