Your devices require applications to serve a purpose. On the Applications menu, several
tabs will give you access to features and sub-menus in order to manage applications
and how they act on your device.
This is the main tab you will be faced when entering the Applications menu. This is where all your
business apps live. You may upload them, check which ones are currently being used, delete old unused
ones, and more. You may also add an optional comment, in case you need to keep track of changes between
application versions.
Once you've uploaded your business apps, they need to be linked to Profiles
in order for them to be distributed to devices in the field.
Permissions
The following list includes all permissions tied to this MDM section and the impacts they have on the MDM interface
or the MDM API.
Some applications have rather simple use-cases, but you might not want to develop them in-house
as they will take time from your developers, which you would prefer be spent on more business-related
tasks. Such applications could be, for example, an app to send and receive SMS messages, or an app
to store contact information on the device.
To address these simple use-cases, Famoco provides what we call "Essential Apps".
If you find a need for these, simply add them to your Profiles.
When manipulating many devices across multiple organizations and fleets, or between different
modes (Production VS Developer), it is possible that some leftover unwanted apps remain on the devices
due to conflicting configurations. On the opposite end, while developing a new application and testing
it on your devices, the MDM will try to uninstall what it considers an unknown application.
Whitelists allow you to ensure that anything not on the MDM profile, or not explicitly listed as allowed
as an exception, will be totally cleaned from the device.
Once you've created a Whitelist, you need to add them to your Profiles
for it to be distributed to devices.
Permissions
The following list includes all permissions tied to this MDM section and the impacts they have on the MDM interface
or the MDM API.
What if you wanted different behaviours for the same app depending on the fleet of devices?
Without building multiple different versions of your app, of course.
App Configuration allows you to do exactly that. Create multiple configuration files and push
them to your different devices. Example: display a different user interface depending on the type of
users between Fleet A and Fleet B.
Please refer to the Developer Docs - App Config sample code page
in order to get more information about how your business apps are able to receive configurations from
the MDM.
Once you've created App Configurations, you need to add them to your
Profiles for them to be distributed to devices.
Permissions
The following list includes all permissions tied to this MDM section and the impacts they have on the MDM interface
or the MDM API.
This feature requires Famoco Layer version 3.19.0 or above.
Sometimes, you might want to provide optional apps to your users (i.e. not force them to install
applications but still present them as viable options). Creating App Stores allows you to decide
which applications to provide and add compelling descriptions to display to your end-users.
Once set up, users will see a new icon on their device's app launcher, from which they can see
these applications and decide whether to install them or not. Please check the corresponding
Famoco Layer user docs page to understand how they're displayed
on the device.
Once you've created App Store configurations, you need to add them to your
Profiles for them to be distributed to devices.
Permissions
The following list includes all permissions tied to this MDM section and the impacts they have on the MDM interface
or the MDM API.