Your use case doesn’t benefit from your own data. There’s nothing you can do that doesn’t require a direct interaction from the server.
I write an audio recording app, and in my app, users have most to gain from their own data. For most people, syncing is basically an afterthought. In this use case, the ability of having your recordings in your phone is the most important thing.
The difference here lies that in my app, the user generates all the valuable data themselves. In your app, nothing valuable can happen without communication with the airline.
But then the post claims that "everything is a synchronization problem" seems should be qualified better.
Also, most of the comments before mine seemed to be in full agreement that yeah, full synchronization would be a silver bullet, even for cache invalidation
there's certainly things to sync in a airline app. Syncing the current schedules of flight is better than saying no flights exist when offline.
But when you're talking a about purchasing whats basically a live interaction with a paid for service, it runs into the verification/authentication aspect which can't be trusted by random customers.
So yeah, there's definitely apps that sync is a rare bit of concern to the customer/user experience.
I write an audio recording app, and in my app, users have most to gain from their own data. For most people, syncing is basically an afterthought. In this use case, the ability of having your recordings in your phone is the most important thing.
The difference here lies that in my app, the user generates all the valuable data themselves. In your app, nothing valuable can happen without communication with the airline.