# Getting Started

# Overview

The following figure illustrates the process of getting started with Esper.

Esper Setup Overview

Each of these steps is described in detail below:

# 1. Sign Up for an Account

Your first step is to sign up for a free trial account. During the signup process you will will be asked to enter a few quick details to set up your environment:

Signup screen

Once you click Start My Free Trial, you'll be automatically logged into your new environment’s Console. You’ll also get an email with your temporary login credentials, along with the URL of your console. (It will be something like foooo.esper.cloud, where “foooo” is the randomly generated 5 letter name of your environment).

Note: Please change your password when you are redirected to your endpoint!

# 2. Upload Your App to the Esper Cloud

When you first enter your Esper Console, there are no apps available. If you want to include your app to include it when you provision your first device, upload it to your Esper Endpoint as an Enterprise App stored in the Esper Cloud. This works with both AOSP and GMS devices. Be sure that your APK is signed with the V1 signature as that’s the signature we check for when apps are uploaded. Upload your app by going to Apps in your left sidebar, and then click the Upload Apps button. Learn more about uploading apps to the Esper Cloud here.

If you're feeling adventurous, upload several versions of your app so you can try out pushing new versions to your device to try out Esper’s app management capabilities.

Alternatively, if you are provisioning a GMS device you can use Google Play apps by setting up a managed Google Play account—you need to first do the account setup before Google Play apps will be available for approval to be used in your Endpoint and for installation on your provisioned devices. Go to Apps, and then click Google Play to get started. Find out more about enrolling in managed Google Play here.

This is an optional step, you don’t have to include any apps when you start—but depending on your use case you may wish to have your Enterprise App available, a desired Play Store app, or any combination of the two.

# 3. Modify Company Shortcode

We use a Device Name to reference devices that are provisioned in Esper. They are mapped to a GUID-based Device ID we use at the API level. The Device Name is displayed on the Home screen of provisioned devices (noting it is possible to remove the Device Name for certain use cases).

We create a system-generated Device Name prefix consisting of 6 characters. If you are unhappy with the system-generated prefix, feel free to change it by going to Company Settings on your left sidebar and then click Edit Profile, the company short code will be at the bottom. Or you can just go with the default prefix. Find out more about Company Settings and the short code here.

# 4. Create a Provisioning Template

Now that you have your very own endpoint, the next step is to create a Provisioning Template. A Provisioning Template enables you to define the initial profile for your devices by specifying the configuration, apps to be loaded, and unique settings you wish to apply. Once you’ve created a template, you can use it to provision as many devices as you need.

To start creating a template, click on the Provisioning Templates link that appears in the left sidebar of your endpoint:

Provisioning Template

Please read Steps to Create a Device Template for more information on this process.

# 5. Provision a Dedicated Android Device

You can use any Android device that meets Esper’s requirements as a target device for your applications and can be provisioned by the Esper Console. Once provisioned, you’ll be able to communicate with your device, and to deploy and test apps on it. During the process of provisioning, an Esper Device Agent will be installed on the device. Please see Provisioning Your Device and follow the process best suited to your device and workflow.

If you are an Android developer and wish to use an AVD, you can easily provision your AVD using the Esper Device Provisioner tool. Simply install the Device Provisioner on your development PC, create an AVD in Android Studio, then run the Device Provisioner to provision the AVD. Find out more here.

You can also create a cloud-based device to try out called a Simulare—this is only available on brand new Esper endpoints. It gives you limited capabilities, but if you have nothing else to try it is an option. We recommend using an actual device or an Android Studio AVD. Once you provision your first Android device or AVD, the option to create a Simulare device is removed.

# 6. Start Using the Web Console

One way to explore and interact with your devices is to use Esper’s Web Console. Once your device is provisioned, you’ll start seeing it on your Console:

Web Console

Here are some of the interesting things you can try out:

  • Define a Compliance Policy (read more here) and then push it out to your device (here).
  • Update an app you installed on your device to a newer version.
  • Initiate a remote view (or if supported remote control) session (read more here).
  • Experiment with a Kiosk mode application (read more here).

Once you get the fundamentals of Esper down, now you can move on to Esper’s Group management capabilities by provisioning additional devices and putting them into the same group.

Please see Esper Console for details on using the Esper Console.

# 7. Start Developing

The first step to Developing with Esper is to generate an API key and obtain the Enterprise ID of your endpoint. The process of acquiring these two has been described in our API Key Management Page. With this information, you can start using the Esper REST Application Programming Interfaces (APIs), Esper Python Software Developer Kit (SDK), or the Esper Command-Line Interface (CLI).

When you begin your app development in Android Studio, you can use the Esper Android Plugin. This will help you leverage the Esper APIs to develop, deploy, and test apps on your target devices.

Note: API keys are tied to individual accounts. Esper's recommended best practice is to create a dedicated account for API keys with the credentials securely stored.

# 8. Get Your Team Involved!

Esper makes it easy to add team members to your endpoint enabling you to give them specific roles down to the Group level.

Feel free to add accounts for additional team members and pass them their credentials so they can join the fun.

Below are quick links to guide you on how to perform specific actions on the Esper platform: