Ketki Jadhav

Device Manager, a web based portal that allows admins to configure and control settings on the Magic Leap One, roll out these devices to employees, deploy private apps and manage login credentials, all in one place.

What does the Magic Leap Device Manager do?

The Magic Leap Device Manager allows admins to configure and control settings on the Magic Leap One mixed reality headset through a centralized web portal. It lets them roll out devices to employees, deploy private apps and manage login credentials, all in one place.

Shown below is a video capture of the settings on the headset which can be configured through the Magic Leap Device Manager.

A Developer focussed company shifts towards Enterprise

Magic Leap is a mixed reality headset company that launched it’s first product in July 2018. The first headset, Magic Leap One- Creator Edition was targeted to developers. At the end of 2018, there were beginnings of internal conversations to shift the target audience towards Enterprise who are more likely to invest in an emerging technology is mixed reality.

A system for managing large number of devices

Shift of target audience meant much larger deals were being anticipated. Magic Leap’s target audience, Fortune 500 companies, usually sign deals for at least 10+ devices. Buying multiple devices especially for official use automatically gives rise to the need for managing and tracking these devices.

Magic Leap Device Manager

And that paved the way for designing Magic Leap’s first enterprise focussed product, Device Manager. Device Manager is a centralized web portal that allows admins to roll out devices to employees. Remotely configure devices, deploy private apps and manage login credentials, all in one place.

Device Manager is designed for users who are in-charge of controlling company devices i.e IT admins of Fortune 500 companies. The copy, tone of voice and experience of the portal is curated keeping in mind people who are familiar with device management suites and their usage.

All the features finalized for the first release ( shown below ) were decided as a combination of research insights, technical constraints, resource constraints and business deals in place.

In order to design a good experience, it was important to understand how all the services talk to each other in the back-end. This allowed me to accurately figure the right type of format for showcasing success and failure states, progress status and management options like delete, undo or retry.

Shown below is the flow for the feature “Creation of profiles”. Each of the 5 features had user flows and low-fidelities mapped out in the same manner.

Being the only designer for the product, I was responsible for the end-to-end designing of the experience. After all the low fidelities were in place. I created high fidelity prototypes using our Component Kit and Brand Guidelines.

This lean and mean team on the right launched Magic Leap’s first enterprise product on the required deadline.

Kiosk Mode

Okta Corporate Login

Designing other touch points

Apart from designing the Device Manager I was also responsible for creating designs for it’s presence and marketing on our online stores. Work involved thinking through the right placement, collaborating with our sales and marketing team to figure the right copy and assets and creating the low & high fidelity prototypes.

I also assisted the marketing, sales and support teams in figuring the business model for the Magic Leap Device Manager. This included thinking through

1. Where does the customer first discover this product and what is the best experience to move them through the pipeline?

2. Where and how does the customer creation happen in the backend? How can we integrate and utilize our other work streams like shipping to make setup of device manager easier?

3. Which features we can and should charge for.

4. Should the users be charged per device, per user or both?

Roadmap Features

While we launched with 5 features, I designed and fleshed out 9 total features. The four other features that I designed include the ones shown below.

1. Fast and efficient creation of provisioning profiles on the Device manager

2. Very few support calls asking for functionality of the product

3. Easy and effortless installation of apps on the devices.

Data driven iterations

A soft internal release was done in September 2019 prior to the official release in December to test the product with our first real enterprise customer. This release helped me advocate for a number of features that were initially de-prioritized from the roadmap because of resource constraints. Some of these included

1. Accommodating small to medium sized business personas ( Education and Government)

2. Pushing for Pagination, global search, filtering

3. Pushing for over-the-air update provisioning of devices

4. Pushing for user based profiles vs device based

5. Rolling in apps into profiles.