Video: https://www.youtube.com/watch?v=n-cxvqXLuh0

Syncing is possible using the sidecar approach. A little service written in Golang watches the mobile clients and detects changes in their configuration. For the sake of simplicity we tested this with a Android Variant where the Google Key is added through a label in the Mobile Client. This is also shown in the Video.

One concern that needs to be answered:

We now have two sources of configuration for the variants: UPS itself and the Mobile Client. This can lead to unexpected behavior: what happens when a user deletes an automatically created variant? Currently it would be re-created in the next sync round. We should probably only have one source of configuration (the Mobile Client) and display a warning when users try to edit a managed variant in UPS.

We should not have two sources of configuration because then we will get into dilemmas like: 'The user changed the config in UPS: should i update the mobile client config with the new information or should i overwrite the user's changes with what's in the mobile client?'

ping David Martin Matthias Wessendorf