Skip to main content

Managing Application Versions

Learn how to manage multiple versions of applications, track version adoption, and control version deployment.

Version Management Overview​

The version management system allows you to maintain multiple versions of each application, providing flexibility for deployment and rollback scenarios.

Version Drop-down Functionality​

The Version Drop-down provides efficient access to all versions of an application.

Accessing Versions​

  • Locate the Latest Version column in the applications table
  • Click the drop-down arrow to view all available versions
  • Versions are sorted in descending order (newest first)

Information Displayed​

For each version, the following information is shown:

  • Version Name – User-friendly version identifier (e.g., 2.1.0)
  • Version Code – Internal version number
  • Release Date – When the version was added to the system
  • File Size – APK file size
  • Device Count – Number of devices with this version installed
  • Download URL – Link to the APK file (if available)

Interactive Actions​

View Version Details:

  • Select a version from the drop-down
  • View comprehensive version information
  • See deployment statistics

Open Download URL:

  • Click on a URL within the drop-down
  • Opens in a new browser tab
  • Useful for verification and manual downloads

Navigate to Devices:

  • Click on the Device Count for any version
  • Redirects to Device Info page
  • Shows which devices have that specific version

Adding New Versions​

Add new versions to existing applications to support updates and improvements.

Steps to Add a Version​

  1. Navigate to the application details page

  2. Click the Add Version button

  3. Choose upload method:

    • Upload APK – Upload new version from local system
    • URL Input – Provide download URL for the new version

  4. System validates the new version:

    • Verifies package identifier matches existing app
    • Checks that version code is unique
    • Extracts version information

  5. Click Confirm to add the version

Version Validation​

  • Package Identifier – Must match the existing application
  • Version Code – Must be unique (not already in the system)
  • Version Name – Should follow semantic versioning (recommended)
  • File Size – Must not exceed 150MB
tip

Versioning Best Practices:

  • Use semantic versioning (MAJOR.MINOR.PATCH)
  • Document changes in version descriptions
  • Test new versions before wide deployment
  • Maintain at least one stable version for rollback

Deleting Versions​

Remove old or problematic versions from the system.

Delete Version Process​

  1. Open the version drop-down for the application

  2. Locate the version to delete

  3. Click the Delete button for that version

  4. A confirmation dialog appears:

    • Shows version name and code
    • Displays device count using this version
    • Warns about permanent deletion

  5. Choose an option:

    • Cancel – Closes dialog without changes
    • Delete – Permanently removes the version

Delete Results​

  • Success – Version removed with success message
  • Failure – Error message if deletion fails (e.g., version in use by a profile)
warning

Single Version Protection:

If an application has only ONE version:

  • The Delete Version button is disabled
  • You must delete the entire application instead
  • This prevents applications from having zero versions
  • Ensures system integrity

Version Deployment Tracking​

Monitor which versions are deployed across your device fleet.

Deployment Statistics​

Access detailed statistics for each version:

  • Total Devices – How many devices have this version
  • Installation Status – Pending, installed, failed
  • Distribution – Breakdown by device type, OS version
  • Adoption Rate – Percentage of devices on this version

Version Adoption Monitoring​

Track Adoption:

  1. View version statistics in the application details page
  2. Click on device counts to see which devices have which versions
  3. Monitor adoption rates after deploying new versions
  4. Identify devices that need updates

Version Control Strategies​

Rolling Updates​

Deploy new versions gradually:

  1. Test Phase – Deploy to small test group
  2. Pilot Phase – Expand to larger pilot group
  3. Production – Full deployment after validation
  4. Monitor – Track installation success and issues

Maintaining Multiple Versions​

Use Cases for Multiple Versions:

  • Compatibility – Different versions for different Android OS versions
  • Feature Sets – Different versions for different user roles
  • Rollback – Keep previous stable version for emergency rollback
  • Testing – Test versions alongside production versions

Version Lifecycle​

Typical Version Lifecycle:

  1. Development – Version created and tested
  2. Staging – Added to MDM system
  3. Deployment – Assigned to devices via profiles
  4. Active – Primary version in use
  5. Maintenance – Bug fixes and updates
  6. Deprecated – Superseded by newer version
  7. Archive – Removed from active use but retained
  8. Deletion – Permanently removed from system

Best Practices​

Version Management​

  • Semantic Versioning – Use MAJOR.MINOR.PATCH format
  • Change Documentation – Document what changed in each version
  • Version Testing – Test thoroughly before deployment
  • Gradual Rollout – Deploy incrementally to minimize risk

Version Cleanup​

  • Regular Review – Periodically review old versions
  • Remove Unused – Delete versions no longer in use
  • Keep Recent – Maintain at least 2-3 recent versions
  • Document Removal – Record why versions were removed

Rollback Planning​

  • Stable Version – Always maintain a known-good version
  • Quick Rollback – Test rollback procedures
  • Communication – Notify users of version changes
  • Monitoring – Watch for issues after updates

Security Considerations​

  • Patch Updates – Deploy security patches promptly
  • Vulnerability Tracking – Monitor for known vulnerabilities
  • Forced Updates – Consider forced updates for critical security fixes
  • Version Auditing – Maintain audit trail of version changes
tip
  • This functionality helps users track application updates and ensure proper deployment across devices while maintaining version control and rollback capabilities.
Last updated on