![]() While installing an app onto a work profile does effectively clone it, using a work profile this way poses some challenges. Most third-party app cloners like Shelter create a work profile because that’s the only kind of profile they can create with the APIs that are available to them and the privileges they can attain. OnePlus’ OxygenOS, for example, creates a dedicated user profile for its “Parallel Apps” feature that it then installs the apps of your choice onto. For the most part, these existing implementations clone apps by installing them onto secondary user profiles. As I mentioned before, many OEM builds of Android ship with their own take on this feature, and there are also plenty of third-party apps that provide this functionality. That’s not to say that you can’t clone apps if your device isn’t running Android 14, though. At least it's clear now that app cloning in the process of being upgraded to actually be usable in Android 14. While the Pixel Launcher in Android 14 DP1 doesn't apply a work profile badge to cloned apps, it doesn't differentiate them at all, and also continues the bug of creating a work profile tab. In fact, the launcher would think your device has a work profile when none might exist at all, cluttering your app drawer with a work profile tab. In earlier releases, the launcher would mistakenly apply badges signifying the cloned apps belonged to a work profile. Cloned apps need to be differentiated from their originals on the home screen in some way, otherwise you’d mistakenly open the wrong app all the time. ![]() However, Android hasn’t offered a way, outside of ADB commands, for users to create that profile or to choose which apps to install apps onto it - until now.Īnother key piece that was missing in prior releases (and is still missing in Android 14 DP1) is launcher integration. Although the “cloned apps” feature is new in Android 14, the clone user profile itself was first introduced in Android 12.
0 Comments
Leave a Reply. |