— 5 min read
mimik provides a SDK platform to third-party developers that enables devices to create distributed edge-cloud clusters by physically discovering and establishing peer to peer connection between one another.
This technology enables ad-hoc and real-time formation of mesh networks across different devices, operating system, and network connections.
The team had developed the initial version of edgeSDK and were considering if they could increase sales by creating an consumer app that would demonstrate how the SDK worke under the hood. I initially joined the team as a designer to help craft the user experience of the demo app, and grew into a Product Management role as time went on.
By sharing a short survey and follow up interviews with the existing user base and stakeholders we learned that:
No data or understanding about who the SDK was for, or who app users are, their behavior, or impressions of application and which features mattered most.
The team had created many proof of concept works to engage potential customers but would not result in a sale because there was no clear definition of which functionality the SDK currently supported.
App use cases could not be fully defined without a SDK road map to indicate when app features could be enabled.
Most internal and external users did not have the latest versions of the application or know how to easily install them.
Capturing insights about the current user's media sharing habits
This insight left the team with more questions than answers so we set out to learn:
Evaluating different opportunities to showcase the edgeSDK.
Capturing and summarizing qualitative feedback collected from usability tests of the current design.
Displaying results of quantitative data collected from task completion tests conducted on the current app design.
Conducting a high-level competitive analysis quantified values and functionality other services offered. This provided an initial framework for evaluating opportunities currently missing from mimik access and what value would be provided to end users.
The initial edgeSDK could only discover and connect with devices on the the current local network. Survey results identified 4 common environments for creating and consuming their personal media.
Storyboards were developed with Indigo Studio to simulate the experiences for the value proposition being tested.
A collaborative approach to designing complex UI flows with a shorthand form document. This low-fidelity approach allowed us to co-create and maintain entire sets of flows that need to be designed in higher fidelity, tested, revised, implemented, tested, and retested.
Flow diagram for how micro-services running on different edgeSDK enabled devices would interact in media sharing scenarios.
Topology of back end services, mobile devices and television set-top boxes (STBs) discovered, connected, and communicated with each other.
Sitemap of the TV application integrated mimik access functionality with a partner's digital TV services.
Wireframes of user interactions using a remote control to browse their personal media library.
Framer Classic prototypes were developed to test user task completion rates using real devices and data.
Architecture diagram displaying how the access application interfaces with the edgeSDK, how edgeSDK instantiates micro-services based on user action, and how edge micro-services utilized the mimik back end infrastructure.
As a result, the team and I were able to challenge our initial assumptions for creating the mimik access applications. This shift in thinking helped us to:
View more of my work or send a message to learn more.