The standalone catalog has limited functionality compared to other catalogs. To decide if it can benefit your deployment, determine how end-users interact with it and if the unmanaged deployment of applications is sufficient. Also, consider what SDK functions your deployment needs.

End-User

  • End-users enroll with AirWatch using the Internet and not with an Agent.
  • End-users must re-enroll with the standalone catalog when you change versions. Even if they do not re-enroll, they still have access to applications. However, they cannot receive an updated version for the catalog unless they re-enroll.

Deployment

  • Devices in your standalone catalog deployment are unmanaged. An unmanaged device does not have the security controls offered by the AirWatch MDM feature.
  • Applications distributed with the standalone catalog remain on devices after an end user unenrolls with the standalone catalog.
  • You cannot track application downloads but you can see a list of assigned applications for the device in the device record in the AirWatch Console.

Available SDK Functions

Supported applications can use limited AirWatch SDK functions when accessed through the Standalone Catalog.

  • SDK profile retrieval
  • User name and password authentication
  • Jailbreak detection
  • Beacon technology support

For more topics about the standalone catalog, see Standalone Catalog for MAM Only Deployments.