Google has shared how they’ll migrate users from the old Play Store version of Health Connect to the new system version in Android 14.
Health Connect is being integrated into the OS as a new Mainline module that’s updatable through Play System Updates.
The migration plan is as follows:
1) Once users update to Android 14, the Play Store version of Health Connect will become inactive.
2) The Jetpack Health Connect library will route the user to the system (module) APIs and block them while data migration is in progress.
3) The migration process starts when the system and Play Store versions are feature compatible. Both permissions & data will be migrated. The Play Store version may need an update to become “migration aware”, whilst the system version may need one to become “feature compatible”.
4) The migration process will commence. Once it’s happening, the system (module) APIs will be suspended with a “migration in process” status. If this process is suspended, it can be resumed by the user.
Data migration “is not expected to exceed 2 hours.” For example, migrating 10 years of running records collected 1 hour every day would take ~4s. Migrating 5 years of heart rate data collected every minute would take ~15 mins.
During migration, the system version will ignore any duplicate permissions or data originating from the Play Store version, in case it started to acquire data and permissions before any migration or cloud-based restore (not announced!) has taken place.
5) After data migration has completed, the user can uninstall the Play Store version. (On Pixels and the Nothing Phone 2, though, the Play Store version of Health Connect is preinstalled as a system app, so it can’t be uninstalled outside of an OTA update.)
OEMs can create a RRO to style the data management and permissions screens for Health Connect. This should be done to bring the app’s UI in line with the rest of the OEM’s skin.
CHUCKYSCARNAGE 