• logo-behance
  • Dribbble-01
  • LinkedIn

Nimble Platform

UI/UX DESIGN | WEB PLATFORM

OVERVIEW

The Nimble platform allows Admins, IT Technician and other types of users to control Nimble devices remotely through the cloud. The primary uses case of the platform is remote device update, device management and device metrics.

 

The Nimble Platform has been designed using Microsoft Azure Cloud Platform and services. We're trying to leverage as many managed services as we can, such as Azure Functions, Azure App Services, Blob Storage, removing our need to manage servers and infrastructure.

MY ROLE

My scope of work was brainstorming with UX Designer, Product Manager to define features based on research, creating wireframes, information architecture, designing interfaces, illustrations as well as providing animations for prototyping.

 

In addition, I worked alongside a UX Designer, Content Strategist, Product Manager, Front-End Developer and Back-End Developer.

STUDY & ANALYSIS

​USER STORIES

Different users will have different use cases for the Nimble platform as there are many types of users along a enterprise smart display solution.

THE SOLUTION

Based on the research, we were brainstorming and prioritizing to define the main features that necessary to implement first based on user’s need and our resources: Organization Management, Account Management and Device Management which allows each type of users to solve different problems:

 

Soda Labs Admin:

+ Responsible for new features, bug fixing and system app releases for the Nimble device.

+ Platform's support and updating external parties on new features and changes.

 

Foxconn Admin:

+ Responsible for a display product line's firmware and hardware.

 

Sharp Admin:

+ Responsible for sales and account management of Sharp's display solutions to small and medium enterprises

WIREFRAMES

After got all of the necessary information, I came up with several rough wireframes that proposed to the team the user flow, information architecture as well as layout for the main features. I iterated these steps addressed feedback from the team until we finalized the best options to go with.

MAIN FEATURES

01. ORGANIZATION MANAGEMENT

The Nimble platform will allow each Brand (Sharp) to create and store all of its clients organization information in a management section. The company information will only be viewable by the Brand that created them.

Organization Types

 

There are main types of organization accounts. There are brands, channel partners and clients. In the situation where there are multiple companies in the channel between Sharp and the Client, all of them are sub-accounts under the main Channel Owner, determined by whoever deals directly with Sharp.

 

●  Brands

Brands would be the owners of the devices themselves. The device will be branded by a company such as Sharp. Sharp will onboard channel partners as well as clients through their own divisions such as SBS (small business solution). For now, we will only be working with Sharp but in the future, there could be more brands like Sharp selling WCDs into their own markets.

 

●  Channel Partners

Channel partners are distributors for the brand and the brand will have less direct access to the end-user organization. The channel partner will take over the role of setting up the Nimble device from the brand and will onboard the device and accounts on their own. Channel partners can have more organizations under its management.

 

●  Clients

Clients are the end-user organization. Clients will only have offices and will not have any organizations under them. Clients will be the user of the product and will either have their own admins to control the platform or rely on the solution provider to help control the platform.

02. ACCOUNT MANAGEMENT

The Nimble platform has a variety of account types and will require a system in which admins can create, update, and remove users on the platform. There will also exist a flow for accounts to verify themselves and have control over their own information.

Account Types

Every account type will have the permissions of all the account types below its own hierarchy. Account admin can add more accounts to its own organization.

●  Soda Labs Admin (SUPER ADMIN)

 Soda Lab admins will be able to control every aspect of the platform. Only Soda Labs admin can add other Soda Labs admin.

●  Foxconn Admin

Foxconn Admin would upload the latest firmware for the WCD.

●  Brand Admin

Can add new locations (company), offices (company office) and accounts for those locations/office of their channel partner/ end clients to the platform.

●  Channel Partner

Can add new locations (company), offices (company office) and accounts for those locations/office of their end clients to the platform.

●  Client Admin

 

Can only add more client admin accounts.

* Account permission hierarchy:

Soda Lab → Foxconn Admin → Brand Admin (Sharp) → Channel Partner (Techdata) → Client Admin (E&Y IT Admin)

02. DEVICE MANAGEMENT

Device management enables the admin to view, update, edit, remove all the devices in the locations that they are responsible for. The admin will be able to filter/sort the devices based on locations that they manage. The admin will need to also be at the device to provision it properly because device provisioning will need the admin to sync the device to the platform.

●   Device Management Screen

The devices can either be view as a grid or a list of devices. Within this screen, the admin will see some of the important base information associated to the device. If the admin wants to dive deeper into a particular device, they can click into any of them and brought to the device detail screen.

●  Foxconn Admin

Foxconn Admin would upload the latest firmware for the WCD.

●  Adding Device / Device Provisioning

The device provisioning step is very important to properly sync a device to the correct organization and office. To seamless add a device for the user without having to enter a large hardware ID or organization/office ID we use a timed digit code for the ad​min.

OTA SERVER

The OTA server has been designed using Microsoft Azure Serverless Architecture. This paradigm wraps our business logic in Azure Functions, removing our need to manage servers and infrastructure. As per the Azure website, here is a general diagram of the technology.

General User Flow

The OTA platform will be used by admins to upload, manage, and push new firmware to the device. Admins must first log into the portal. Once inside, admins can perform actions such as upload firmware, download firmware, manage device listing.

Firmware Upload

Admins will upload firmware to the portal and input all of the information about the firmware. This information is required in order to ensure proper OTA file management. Once uploaded, the file will be stored using Azure File Storage and the resulting file metadata will be stored in the Azure Cosmos DB.

UI LIBRARY

Since our platform requires more features in the future and we need to reuse as well as scale the design, the UI library was created to help me hand off the design to our engineering team, help them easier to build a clean, consistent user interface.

THANKS FOR SCROLLING!

Made with a lot of coffee and music.