In this chapter, we discussed different ways of dealing with a split-brain: the collective agreement approach where every collaborator must agree on the same resolution and the self-appointed dictator approach where any collaborator can choose a resolution independently of the others. We implemented the second approach for the description field of the to-do items and discussed ways to extend this to the map and image fields as well.
In the next chapter, we'll look at ways to optimize the performance of the app. Up until now, we've stuck with the standard defaults provided by our offline database. Let's investigate where our defaults fall short and how to improve them. We'll also learn how to detect different usage scenarios and tweak the defaults in real time to accommodate these scenarios.