# Data Synchronization - Kevin Galligan

DevFeed: [Data Synchronization - Kevin Galligan](<https://devfeed.tech/articles/data-synchronization-kevin-galligan-38147.md>)

Original publisher: [Read original article](<https://touchlab.co/6658>)

Published: 2012-08-16T04:46:00Z

Content type: opinion

Language: en

Sources: [Touchlab | Enterprise Mobile Innovation & Development](<https://devfeed.tech/sources/touchlab-enterprise-mobile-innovation-development.md>)

Topics: [data](<https://devfeed.tech/topics/data.md>), [SQLite](<https://devfeed.tech/topics/sqlite.md>), [Android](<https://devfeed.tech/topics/android.md>)

Tags: [android](<https://devfeed.tech/tags/android.md>), [callback](<https://devfeed.tech/tags/callback.md>), [client](<https://devfeed.tech/tags/client.md>), [data](<https://devfeed.tech/tags/data.md>), [framework](<https://devfeed.tech/tags/framework.md>), [sqlite](<https://devfeed.tech/tags/sqlite.md>), [synchronization](<https://devfeed.tech/tags/synchronization.md>), [thoughts](<https://devfeed.tech/tags/thoughts.md>)

## AI overview

The article argues that data synchronization, particularly between a mobile client and a server, is highly app-specific and difficult to generalize. It suggests that seemingly automatic synchronization systems would ultimately require application-specific rules and logic, while noting that the discussion does not cover multi-device synchronization or server-push systems.

## Source excerpt

There are topics for which I claim to be an expert. This is not one of them. I say this because its one of those things that doesn't seem to have a fully graspable scope. I'd say I'm somewhat of an expert on SQLite and Android. Its easy to say that because there are a limited number of topics about which one might care about, and if there's something specific that needs research, you can kind of "dig it out" and test it. One can grasp the scope.