Draft of enrolment use case

[btry]

The enrollment process for Apple devices is very different from what we did for Android and the freedom provided by this platform.

I need to send a xml file to devices from the backend. To keep a good enrollment UX I suggest to stick as close as possible to what we did for Android.

The deeplink in the email should allow us to detect the operating system and redirect the user to the accurate app store (google, apple, ...).

Once the agent installed, the backend will receive API requests. Only from this step we can determine the type of MDM (android, apple for now).

When the agent sends a HTTP GET to read its entry in PluginFlyvemdmAgent, I can customize the HTTP answer depending on the mdm type. I can s end the XML data, and the agent needs to show it as a file to the user. The user must tap it and the iOS will display some metadata and ask for installation of the file (handled by the OS).

Once the profile installed, the backend will be able to send other profiles for configuration, policies, ...