Case Study · 01

Bytebeam Cloud
Platform

A comprehensive redesign of the Actions dashboard for an automotive IoT platform — improving usability, reducing errors, and scaling for enterprise device management.

Product Design Dashboard UX B2B IoT

Role

UI/UX Designer — Requirements gathering, prototyping & design in Figma

Duration

Oct 2023 – Ongoing

Team

Ravi Teja (CTO) · Pranav Kumar (Sr. Frontend) · Isac Sam (Graphic) · Krupali Jain (UI/UX) · Frontend Team

4+

Major Features Redesigned

6

Design Changes Shipped

B2B

Enterprise IoT Platform

Connected Vehicles

The Project

What is Bytebeam?

Bytebeam is a comprehensive platform designed to optimize connectivity and data management for connected vehicles. It serves fleet management, vehicle health monitoring, predictive maintenance, battery monitoring, driver monitoring, and over-the-air (OTA) updates.

Key capabilities include remote diagnostics, data analytics and visualization, and error analysis for efficient troubleshooting — all within a single cloud dashboard used by engineering teams.

Fleet Management

Real-time monitoring and control across large connected vehicle fleets and devices.

OTA Updates

Over-the-air firmware deployment with phased rollout and version controls.

Predictive Maintenance

Analytics-driven alerting before device failures occur in the field.

Remote Diagnostics

Deep error analysis and live device state visualization in the cloud.

The Problem

Four pain points,
one broken workflow.

With a growing number of active devices on the platform, the Actions tab required an upgrade — to handle load, incorporate new features, and eliminate user errors that were becoming increasingly costly.

01

Insufficient Action Overview

Users were only notified of executed actions — with no visibility into current status or ongoing operations.

02

Broken New Action Workflow

Multiple stages involving numerous stakeholders, with no structured approach — creating operational chaos.

03

Errors in Rolling Updates

Different vendors for different tasks made tracking progress across device groups extremely difficult.

04

Basic Filter Criteria

Limited filtering forced users to manually search and note down each device — a slow, error-prone process.

Discovery

Starting with
the right questions.

We began by gathering structured feedback from existing users — engineers and fleet managers who relied on the platform daily. These questions guided our research sessions:

01How do you currently manage the devices?
02Who is responsible for managing and monitoring the devices?
03What are the limitations of the current process?
04How many devices do you monitor or manage simultaneously?
05What actions are required on connected devices?
06How often do any actions need to be performed?
07What errors could be encountered while performing an action?
08What parameters indicate that a device is healthy and working properly?
09Are actions on all devices performed simultaneously?
10How many actions can be run simultaneously?

Design Changes

Six changes.
One cohesive system.

01

Action Overview

Enhanced Action Summary

The action view was restructured to give users a complete picture of ongoing and completed operations — not just what ran, but what's happening now and what failed.

Before

  • Only showed executed actions
  • No status visibility on ongoing operations
  • No failure notification system

After

  • Sub-tabs: Live Actions vs Action History
  • New widget for action failures and root causes
  • Clear distinction between ongoing and completed
Old Design
New Design

Before → After: Action Overview redesign

02

Phased Roll-out

Dynamic Icon Integration

The phased roll-out feature introduced additional segmented information. Dynamic icons were implemented to draw attention and provide immediate visual feedback on current status — making the interface intuitive at a glance.

Phased Roll-out

Dynamic icon system for phased rollout status

03

New Action Form

Progressive Disclosure

When initiating a new action, users configure multiple parameters. Progressive disclosure maintains user focus by presenting information in a structured, manageable sequence — left to right, simple to complex.

Advanced features like Phased Rollout, Advanced Trigger, and Auto-Retry are hidden until the user opts in — reducing cognitive load without sacrificing capability.

Progressive Form Step 1
Progressive Form Step 2

Progressive disclosure form — simple → advanced

04

New Action Form

Summary Screen

The length and complexity of the form increases the risk of user error. A summary screen at the end allows users to review all inputs before final submission — acting as a last checkpoint before fleet-wide operations are triggered.

Summary Screen

Review & confirm before final submission

05

Error Handling

Minimizing User Errors

Running actions across large device fleets often creates overlaps with devices already engaged in other operations — leading to system errors. An 'Undone' action state was introduced, allowing users to defer conflicting devices. A button opens conflicting action details in a new tab for informed decision-making.

Error Handling

Conflict resolution dialog with 'Undone' state

06

Filter & View

Advanced Filter Function & View Options

Managing thousands of devices requires smart filtering. Each device has two identification parameter sets — Metadata and Device Shadow. A percentage-based filter lets users select subsets of devices for bulk operations. Filters are context-sensitive across sections of the interface.

1

Step 1

2

Step 2

3

Step 3

4

Step 4

5

Step 5

Steps 1–4: Filter selection flow. Step 5: View options panel.

Talk?

↳ Let's connect

Have a project
in mind?

designer.kj1411@gmail.com