The Esper DevRel 45 release is a small-but-mighty set of changes. Our DevOps team has delivered all-new API capabilities to give Android developers more programmatic power than ever.

Here’s a quick look at what’s new in DevRel 45

  • API for Content Management
  • Exposed Reboot APIs in the Device SDK
  • Plus, Bug Fixes and Improvements. 

1. Content Management API

We added a new API that allows users to programmatically upload or transfer file(s) to devices and device groups –  including config files and other file formats, to devices and Android device groups

This API is critically-important for enterprise device management, since it allows customers to share content in an efficient, secure manner. 

With Esper’s new Content Management API for Android, customers can:

  • See the file transfer history for respective devices. 
  • View the status of a file transfer – success, failure, or in progress – and status details. 
  • Schedule the transfer of one or more files to group(s) or device(s).

Read our full API documentation here

2. Exposed Reboot APIs on the Device SDK

Device reboot has now been exposed within the Esper device SDK.  Now, programmatic reboot capability can be engineered into any third party apps locally running on the device. 

If an Esper customer wanted to reboot a device daily at 5pm, the logic of an enterprise Android app could call Esper’s SDK API to trigger a scheduled, daily reboot. Or, if an app was showing abnormal behavior or a customer’s network was down, it’s now possible to reboot the device as a troubleshooting mechanism to fix local app issues. 

Here’s more info on Esper’s Device SDK

3. Trigger Settings Actions for Offline Devices

We now have actions in settings enabled for offline devices as well. If a command is triggered for an offline device, it will remain queued for 24 hours unless the device comes online earlier and changes are applied.

Bugs and Improvements

  • Customer device provisioning time is now improved, since we’ve prevented unnecessary installs of Google Chrome from Play Store during the provisioning process. Installation is skipped if Chrome is preinstalled on the device. 
  • When the USB connectivity option isn’t enabled, it won’t allow any external device to be mounted via USB or SD card insert. So, we renamed the External Device field in the Provisioning Template to make it clear that it remotely allows or disallows USB and SD mounts.   
  • A customer was having trouble uninstalling a device app after first disabling and then enabling the same app. Now, this issue is fixed. 

And, that’s it for DevRel 45. Stay tuned for another round of customer improvements and fixes in DevRel 46, scheduled for the third week of October 2020. 
What do you think? We’d love to hear your honest thoughts on how to make your Esper customer experience better in DevRel 46, 47, and beyond. Please share your feedback with us directly: