• Product Designer


  • Figma


  • Whole design process: 1 months

Autonomously report device status updates with Apple's new protocol

During Apple's Worldwide Developers Conference '23, Apple released a new protocol called Declarative Device Management. This new protocol, running on iOS 16 or later allows devices to be proactive, and autonomously report their status. This protocol significantly reduces network traffic, decreases the latency of device status updates, and empowers the device to maintain compliant states even when offline.


Time crunch to integrate a platform specific protocol within a platform agnostic system before other Mobile Device Management (MDM) products

DDM protocol challenges MobiControl's system architecture. MobiControl, being a platform agnostic product does not prioritize one platform over another unless forced, although the goal is also to entice users building Apple profiles to utilize the tools under this new framework. Therefore, this challenges development to weave this protocol within the existing system

How might we roll out DDM offerings ahead of competitors to allow users to leverage Apple's new protocol, while being compliant with MobiControl's system architecture

Solution? Keep the existing architecture of Profiles as 'Reactive', while providing users the ability to select 'DDM' as the new flashy Profile type

By allowing users to create DDM as a Profile type, development is able to leverage existing front-end components as opposed to breaking and reconstructing the current Profile architecture. With this, DDM offerings in MobiControl are able to hit the market sooner, and users can begin to use it's benefits.

Early fork between previously used Reactive and newly integrated DDM Profiles

  • Allow the user to make a choice between DDM (new) and Reactive (old) protocol types

  • Inform the user of the difference between protocol types

Up-front, just another Profile... under the hood, DDM magic!

  • DDM Profile utilizes Reactive structure, while only making minor additions to cut down on costs

  • Reactive Profile structure stays the same



Technical research

Explore user flows

Stakeholder decision


Kick-off meeting

  • Briefed on DDM and it's 4 tools; configurations, assets, activations, management

  • 1 week design time for phase 1, with multiple options for point of entry

  • Benefits to user

  • Time to market brings technical constraints

  • DDM as a concept will likely scale to other platforms within the future

Technical research

  • With many of DDM's configurations and assets being similar to MobiControl's current profile creation tools, they can replace the old tools to make profile creation more simple

  • Management and activations are new concepts to enhance the ways in which settings are pushed to the device

Exploring user flows

  • All recipes have ingredient lists between 5-8 ingredients to save time and reduce cooking anxiety.

  • Allows users to generate recipes using ingredients they have on hand.

  • Auto generated meal plans to reduce planning time, and encourage cooking in advance.

Deciding on the best solution

  • Wrap new tools within a profile of type DDM

  • Present DDM configurations as reactive profile configuration

Learing outcomes

  • The experience of utilizing external frameworks and weave it into a system in a way that makes sense to current users


DDM is a protocol provided by Apple. Therefore, originaly the plan would be to group all tools together for the user to manage. After thinking outside the box and pulling the different tools apart, it was evident that this was not the right direction and each tool could be mapped to different configuration settings within MobiControl.