Jamf Setup & Reset
Companies large and small use Jamf Pro to manage their fleet of Apple devices. Jamf Pro allows IT administrators to remotely send commands and configurations directly to those devices, so users can remain productive. We wanted to leverage Jamf Pro’s relationship with enrolled devices to offer a personalized, secure experience on a shared device. A pair of iOS apps, one for the configuration and one for the resetting of the device was the Product Owner’s solution.
How can we leverage Jamf Pro’s relationship with enrolled devices to offer a personalized, secure experience on a shared device?
- Some Organizations may elect to allow employees to share devices for work purposes.
- This presents a challenge for IT as each user wants their work and personal information to remain private even when leveraging a shared device.
- Expecting each user to have the know-how to manually configure or reset their device each time is impractical
- Requiring IT to manually do so can be tedious and unrealistic as IT may not always know who is accessing what device and when.
User & Audience
The target users of the Jamf Setup and Jamf Reset apps are those that leverage an iOS device to complete their daily work responsibilities.
- There is a good chance that the user has never heard of Mobile Device Management or know what Jamf Pro is.
- They will be familiar with iOS and know how to leverage it to complete their daily tasks.
- Simplicity and a native iOS feel will be important to these users as they will want to spend as little time as possible configuring the device so that they can focus on work productivity.
Team & Role
I was the primary UX Designer for both the Setup and Reset apps. I worked extensively with:
- The Product Owner to capture requirements.
- A UX Researcher to test user flows and interactions
- 2 iOS Developers to insure that everything designed and tested made it to the final apps.
The Design Process
Configuring an individual device for multiple unique users was not a new problem. We knew there was desire for this functionality from feature requests as well as through partnerships with customers.
We started Jamf Setup with a prototype application that allowed end-users to apply settings back to Jamf Pro from their devices.
Instead of applying settings on an individual basis, we restructured the prototype to present the user with a simple list of familiar options that would map back to Configuration Profiles in Jamf Pro. The user would pick a profile and all of the settings and configuration would come to them.
With the new prototype in place we developed a realistic workflow that a user might follow before and after a shift.
The restructuring of the prototype app for Jamf Setup simplified the user flow significantly, so much so that we were left with a one screen application. We knew that Jamf Reset would be just as simple.
Armed with our prototype app and workflow we matched each step in the workflow with an interaction to build our User Flow.
Each app consisted of a single interaction point and required two distinct actions before any backend process began. We worked to make the experience of using the apps feel like they belonged together and were the ‘bookends’ of using an iOS device as a tool to complete their daily tasks.
At this point we had a prototype app, a workflow, and our User Flow, so it was time to start pushing pixels.
Here we began taking into account possible errors and failures on the backend of the application and how to relay such information to the user.
Once we were happy with our user flows we built an end-to-end static prototype to test everything we had designed.
A series of user tests were ran using our InVision prototype. Results were favorable, so the iOS Developers took the screens and began building the final apps.
We leaned heavily on the Apple iOS Interface Guidelines as we wanted the experience to look and feel as close to native as possible.
The apps were designed with generic branding in the form of a banner graphic and a matching button color. We also had to take into account that these apps would have customization options. The IT Administrator that managed the apps would have the ability to add their own branding via the Managed App Configuration (MAC) File. Customization included:
- replacing the banner graphic
- changing the background and button color
- modifying the headline and body copy
We provided some constraints (max width and height of the graphic and the number of lines of copy) and I took care in the layout so that the iOS Developers could leverage Auto Layout for consistent rendering.
Because we wanted to maintain a native feel, the interactions needed came directly from iOS.
We also used a Navigation Bar to allow navigation to the previous page
The final interaction proved to be the most complicated to solve. Once the configuration was received and executed how should the user exit the app to use the device? iOS Guidelines specifically state that an app cannot be closed automatically, as it equates to the app crashing. Our solution ended up coming directly from the final screen in the installation of iOS on a device... Instruct the user to press Home Button.
Jamf Setup and Reset were given to partners for Beta testing. Feedback was positive so they were released into the Apple App Store; you can see Jamf Setup here, and Jamf Reset here. The apps are also marketed as a Technology Solution on jamf.com. Jamf has applied for patents for both applications.