Managing a fleet means living in the details — knowing exactly what's on each device, reaching the right endpoints at the right time, and trusting that your reports say the same thing everywhere. This release brings a batch of improvements across Device Management and App Distribution that do exactly that: more control over Android and eSIM, better visibility into certificates, and cleaner, more consistent reporting.

Here's everything that's new. 👇

📱 Device Management

🔔 Send push notifications to Android devices

You can now send a push notification straight to Android devices that will be handled by the Applivery Android Self-Service App — either as a single action on one device, or in bulk across many at once. It's a direct line to your managed devices when you need to reach them without waiting.

⚙️ Managed configurations for AOSP apps

AOSP apps now support managed configurations, so you can pre-define and push app settings remotely instead of configuring them by hand on each device. Same centralized control you already have for Managed Google Play apps, now extended to AOSP.

📶 More eSIM management options

Two new capabilities for devices with eSIM:

• A command to retrieve the EID (the unique identifier of the device's embedded SIM).
  ​
• A wipe data flag to control eSIM data handling during a wipe.

🔐 Certificate Report History (Android EMM)

You can now consult the history of certificate reports for Android enterprise devices, not just the latest state. This unlocks timeline/history views and lets you inspect past certificate report snapshots in detail — with sensitive identity data automatically redacted so reports stay safe to share.

🌳 Segment tree keeps your "Show children" selection

The segment tree now remembers your "show children elements" setting, so the view you set stays applied as you work instead of resetting on every new session. A small change that saves a lot of repeated clicks.

📊 Unified report configurations across native agents

We've standardized the report descriptions and configurations across the native agents, so the same report means the same thing no matter which platform you are configuring — less ambiguity, easier cross-platform reporting.

📦 App Distribution

🖥️ See device and platform in Downloads

The Downloads view now shows the device and platform for each download, giving you clearer visibility into exactly where and on what your apps are landing.

Most MDM solutions are built around Android Enterprise and Google Mobile Services. That works great for standard devices — but what about your rugged terminals, industrial PDAs, point-of-sale hardware, and digital signage that ship without GMS?For organizations deploying these devices at scale, management has historically meant fragmented tools, vendor-specific workarounds, or simply giving up on centralized control.Not anymore.Applivery now supports full MDM for AOSP devices — Android devices that run without any Google dependency. No Google account. No Android Enterprise setup. No Managed Google Play. Just the same Applivery Dashboard you already use.

⚙️ Key Capabilities

• Kiosk Mode — lock a device to a single app or a curated suite, with full control over the navigation bar, status bar, and power button
• Silent App Distribution — install, update, and uninstall APKs directly from the Dashboard, no Play Store required
• Policy Enforcement — password complexity, keyguard restrictions, factory-reset protection, remote wipe, and 80+ configurable settings
• Wi-Fi & Certificate Management — silently provision corporate networks (Open, WPA, WPA-Enterprise with EAP-TLS, PEAP, and TTLS)
• Always-On VPN — force all device traffic through a corporate VPN with optional lockdown mode
• Remote Commands — lock, reboot, reset password, clear app data, and disenroll devices in real time
• OEM Configurations — extended support for Zebra, Bluebird, Samsung Knox, and other AOSP hardware
• Factory Provisioning — pre-install the Applivery DPC in an OEM image and provision devices automatically at first boot

📌 Use Cases

• Retail and logistics fleets running ruggedized Android terminals
• Point-of-sale and self-service kiosks
• Industrial and warehouse PDAs without GMS certification
• Digital signage and fixed-purpose devices
• Any OEM Android build requiring dedicated device lockdown

🔜 Coming in June 2026

• Remote Support & Control — view and control AOSP devices directly from the Dashboard
• Advanced Kiosk Launcher — Basic and Advanced Launcher modes for AOSP
• Work Profile on AOSP — separation between corporate and personal data on non-GMS devices
  ​

📖 Ready to get started? AOSP management is available on all Applivery plans. Learn more here and contact your Customer Success Manager to get it enabled in your Workspace.

We're making an update to how tag-based filters work in App Distribution to improve overall platform performance.

🔎 What's Changing

Tag filters in builds will now require an exact match, including capitalization. Until now, tag searches were case-insensitive, meaning Release, release, and RELEASE would all return the same results. In the coming days, only an exact match will return results.
This change affects build tag filters specifically. Partial device searches will continue to work as before, with case-insensitive matching still supported.

📌 What You Need to Do

Review your current tag naming conventions and make sure the tags you use in filters match exactly — including uppercase and lowercase letters — the tags assigned to your builds.
For example, if your builds are tagged Production, searching for production or PRODUCTION will no longer return results. You must search for Production exactly.

⚙️ Why We're Making This Change

This update is necessary to address a performance issue. Exact matching allows us to maintain a faster and more reliable experience across the platform.

We’ve introduced Smart Attributes, a new capability that allows you to define and manage custom attributes associated with devices.

This feature enables more precise targeting and dynamic segmentation across your device fleet.

⚙️ Key Capabilities

🏷️ Custom Attributes

Define attributes tailored to your organization (e.g., location, department, usage type).

🔄 Dynamic Assignment

Assign and update attribute values per device as needed.

🎯 Integration with Device Audiences

Use Smart Attributes as filtering criteria in Device Audiences to enable dynamic grouping.

🧠 Flexible Targeting Logic

Combine Smart Attributes with existing filters (e.g., OS, model, tags) for advanced segmentation.

🔍 Why It Matters

Smart Attributes allow you to move beyond static configurations and adopt a more flexible, scalable, and data-driven approach to device management.

Whether you’re organizing devices by business unit, region, or use case, Smart Attributes make it easier to apply the right actions to the right devices — at the right time.

📌 Use Cases

• Device classification by business unit, location, or ownership.
• Conditional policy or configuration targeting.
• Gradual rollouts based on custom-defined segments.

Smart Attributes extend the device data model, allowing administrators to implement custom segmentation logic without relying on static structures. This improves scalability and flexibility in large or complex environments.

💡 Enable It Today!

Smart Attributes are only available on Enterprise plans. If you’re not sure which plan you’re on, check the pricing page or reach out to your Customer Success Manager.

👉🏻 You can learn more about Smart Attributes here.

We've completely reimagined the Applivery Android and iOS MDM Agents. Version 2.0 goes far beyond background telemetry — it now puts a full corporate app store directly in the hands of your end users, without compromising IT control.

No more tickets. No more manual installs. Just the right apps, available on demand.

⚙️ Key Capabilities

📦 Application Catalog

End users can browse, install, update, and uninstall corporate apps directly from their devices. Apps are synced automatically from your Applivery Policy — no web console required on the user side. Corporate APKs are silently sideloaded from Applivery servers; Play Store apps open natively in Google Play with real-time status sync back to the agent.

🔄 Over-the-Air Updates

A dedicated Updates tab surfaces all apps with a pending version bump. Users see exactly what needs updating and can act immediately. Admins retain full control over which versions are available.

🔖 Bookmarks

Share internal URLs, web tools, and documentation with your fleet — organized by category and always up to date via managed configuration. No more pinning links in Slack.

📊 Status Dashboard

Users get a real-time view of every management agent running on their device: Location tracking, App Usage, Data Usage, Network Signal, and Resource downloads (see OS-specific reports for more details) — with green/gray/orange health indicators and last-sync timestamps. Less noise for IT, more transparency for users.

🛡️ Full IT Control

Every section of the portal (Applications, Bookmarks, Status, Files, Notifications) can be independently toggled per device or device group via managed configuration. Set a default view, restrict what users see, and push changes silently — all from the Applivery Dashboard.

📌 Use Cases

Frontline & field teams

Give warehouse, retail, or field workers instant access to the tools they need, without waiting for IT to push installs remotely.

BYOD / COPE

Let employees self-serve corporate apps within a controlled, policy-enforced environment.

App rollouts at scale

Reduce helpdesk load during large app deployments by empowering users to install on their own schedule.

Distributed IT teams

Surface device health status to users directly, cutting down on "my tracking isn't working" support tickets.

Internal resource sharing

Replace ad hoc link sharing with a curated, always-current bookmarks section tied to your managed config.

The Self-Service Portal is fully controlled through your existing Android and iOS managed configuration policy in the Applivery Dashboard. Feature sections are toggled individually, default views are configurable, and the entire experience is invisible to users unless you enable it — so you can roll it out gradually.

⚠️ Minimum requirements

• Android 7.0+ · Fully managed or work profile devices · Applivery Android MDM Agent v2.0.0
• iOS 16.0+ · Applivery iOS MDM Agent v2.0.0

📚 Full documentation is now available for both Android and iOS MDM Agents.

If your organization enforces SSO-only authentication, sharing a build with an external freelancer, QA studio, or partner has always meant a compromise: either create exceptions in your identity configuration or ask external users to go through an authentication flow they don't have access to.

Neither option is acceptable when compliance is non-negotiable.

OTP (One-Time Password) access solves this. It lets you grant temporary, identity-verified access to any external user — at the publication level — without touching your global SSO configuration.

⚙️ Key Capabilities

📧 Email-based allowlist

Add the email addresses of authorized external users directly to a publication. No Applivery account or SSO enrollment required on their end.

⏱️ Time-limited, single-use codes

OTPs are valid for 5–10 minutes and cannot be reused. Each access attempt requires a fresh code, ensuring no credentials can be shared or replayed.

🔁 Single-use access

Optionally remove an email from the allowlist after the first successful download, enforcing strict one-time access. Re-adding is always possible if needed.

⏳ Temporary user lifecycle

OTP users are created automatically and auto-deleted after 30 days. Existing workspace users are never counted twice.

🔔 New build notifications

When a new build is published, OTP users on the allowlist can receive a notification email with a fresh code — no need to re-request access manually.

📅 Combine with Expiring Publications

Pair OTP access with an expiring publication for a fully time-bounded and identity-verified external sharing flow, with zero manual cleanup.

📌 Use Cases

• External freelancers or contractors: One-time build review without creating permanent accounts.
• External QA studios: Time-limited access to a beta without relaxing global authentication.
• Partner or customer previews: Share a specific build securely with a named list of recipients.
• SSO-enforced organizations: Distribute externally without creating SSO exceptions or compromising your identity policy.

📚 You can learn more about OTP by following this link.

If you have any questions or need more information, please contact your Customer Success Manager.

Starting in April, we will introduce a new limit on the maximum number of publications per app within App Distribution. This change helps keep app distribution organized and aligned with each subscription plan.

New limits per plan

📦 Starter: up to 3 publications per app

📦 Essentials: up to 5 publications per app

📦 Startup: up to 15 publications per app

📦 Business: up to 30 publications per app

📦 Enterprise: up to 50 publications per app

These limits apply to the number of publications that can be associated with a single app in App Distribution.

👉🏻 To optimize the use of your App Publications, check out our best practice recommendations.

If you have any questions or need more information, please contact your Customer Success Manager.

We’re excited to announce that you can now manage Private DNS settings on fully managed Android devices (Android 10 and above) through AMAPI. This feature allows you to control how devices connect to DNS servers securely and enforce network policies across your fleet.

Key Details

🌐 Private DNS Mode Options:

• USER_CHOICE: The user can configure private DNS.
• AUTOMATIC: The device automatically uses the network-provided DNS over an encrypted connection. Users cannot modify this setting. Supported on fully managed devices and work profiles on company-owned devices.
• SPECIFIED_HOST: The device uses only the DNS server specified in Private Dns Host. Users cannot change this setting. If you select this mode, Private Dns Host must be set.

🛠️ Private DNS Host:

• Optional field required only when Private DNS Mode is set to SPECIFIED_HOST.
• The hostname must correspond to a supported DNS server. Non-compliance is reported if the host is invalid, the device is not on a network, or other restrictions apply (e.g., unsupported Android version or management mode).

⚠️ Non-Compliance Details:

• Devices not meeting the requirements will report a NonComplianceDetail, specifying the reason (e.g., invalid host, unsupported management mode, Android version <10, or pending network connection).

This new setting helps you enforce secure network connections, control DNS usage, and maintain compliance across your Android fleet.

We’re sharing an important update regarding a recent Android Management API change. An experimental API field, allowedDaysWithoutUpdate, was unintentionally exposed and will be reverted next week to ensure proper platform behavior.

The rollback is scheduled to be fully deployed by Friday, March 6.

Impact

Once this change is live, any policy that includes this field will be rejected in its entirety.

Action required

If you have started any integration or release that relies on this field, please remove it from your policy configurations to remain aligned with the supported APIs.

We want to inform you that Skype for macOS has been removed from the Applivery macOS App Catalog.

Microsoft officially discontinued support for Skype over a year ago and transitioned its communication platform to Microsoft Teams, which is now the recommended and actively maintained solution.

🔎 What This Means

• ❌ Skype for macOS is no longer available in the catalog
• 🔄 Microsoft Teams is the supported alternative
• 🛠️ Existing deployments of Skype will not receive updates or support

We strongly recommend migrating any remaining Skype workflows to Microsoft Teams or another alternative solution to ensure continued functionality, security, and support.