In order to avoid Android's draconian battery saving tactics, replication should be scheduled using Android's WorkManager.

Android devs should be discouraged from using continuous replication, ever, because it won't work.

The intention of continuous replication is that the local DB is kept up-to-date, "in the background", without user intervention. That kind of describes a WorkManager task.

I can see very specific uses of continuous integration, while an app is in the foreground. I think, for instance, of apps supporting ticket-takers or something like that. In those cases you won't need a foreground service.

When the app is backgrounded, I think the WorkManager will provide the behavior that most devs expect.