Not only are we now showing the participants for each shared reminders list in the root view of our app, but we were able to compute all of that information directly in our database query. That allowed our views to become super simple. They just display the data handed to them. And it even allowed our feature logic to be quite simple because it already had the data it needed to do its job. It didn’t need to execute extra queries just to figure out what to do.

And we are now nearing the end of this series of episodes, and in fact we’re near the end of our Modern Persistence mega series. But our SQLiteData library has so many little features that are packed into it that are easy to miss, we wanted to dedicate one last episode to showing off a grab bag of techniques that you can employ in your apps.

The first technique we will show off is how to explicitly tell the sync engine to synchronize any pending changes, including the data stored locally and data stored remotely. 99% of the time you don’t need to think about explicitly synchronization because the sync engine does all the work for you. But there are times you may want the explicit behavior, and luckily we expose all of that information for you.

Let’s take a look.