Skip to content

Secure Browser (BaaS) UI Design

Duration: 3 Months
UI Design
Figma
UX Design
Secure Browser
Security Settings mockup showing settings panel with different panels for privacy protection and appearance | Secure Browser Project
File Explorer | Secure Browser Project
Components for the Secure Browser Project
Mockups showing the default status for the banking platform and a system message | Secure Browser Project
Screens are based on the original prototypes and have been adapted for confidentiality

Overview

This project focused on the UI design of a secure, enterprise-grade browser platform, developed as a Browser-as-a-Service (BaaS) solution.

The platform can be understood as a Chrome-like environment, built for organizations that require strong security boundaries, role-based access, and multiprofile workflows.

Working closely with a UX Lead, I helped define a flexible interface system that supports secure task execution, profile switching, and contextual access to tools and information based on user permissions.

The client brought us on as a two-person design team (two UX Leads and myself as UI designer) to build the platform’s interface directly, with no separate budget for user research. Progress was validated through weekly stand-ups with the client, walking through the evolving design and adjusting based on their feedback.

Design approach

The interface was designed as a modular and layered system, separating security-related controls from application content. This approach allowed the platform to remain flexible and adaptable as the product evolved.

Particular focus was placed on:

  • Designing UI patterns that can scale with increasing complexity.
  • Making system state and security context understandable without overwhelming the user.
  • Supporting efficient workflows for users operating across multiple profiles or access levels.

All design decisions were made with the understanding that the product was still in progress and that the UI needed to support future iteration and expansion.

Role & Responsibilities

I was responsible for expanding the client’s initial idea into a complete UI framework and defining how users would interact with complex, security driven components while keeping the experience clear and usable.

My responsibilities included:

  • Defining the overall interface structure and layout logic.
  • Defining how users navigate, access settings, and interact with complex components such as the internal workspace and file management experience.
  • Building a large component system covering both high-level sections and detailed UI elements.
  • Producing high-fidelity prototypes to support validation and development.
  • Stress-testing the platform to determine how it would behave under certain circumstances such as having a large number of tabs open at the same time, or having to switch between many profiles rapidly.
  • Presenting the design process and final outcome and discussing future steps with the UX lead and the stakeholders on a weekly basis.

In total, I designed more than 175 UI components, ranging from large structural elements to smaller details such as buttons, icons, states, and system feedback.

Sketching for the Secure Browser Project
Sketching for the Secure Browser Project
Sketching for the Secure Browser Project
Sketching for the Secure Browser Project
Sketching for the Secure Browser Project
Sketching for the Secure Browser Project
Sketching for the Secure Browser Project
Sketching for the Secure Browser Project
Concepts for the initial components and structure

Outcome

The project resulted in a complete UI framework, reviewed and approved by the client through our weekly stand-ups, and handed off to their IT team for development.

The deliverable was structured as a presentation paired with a Figma file, broken into sections by platform area. 

Each section documented its required components and their use, the design principles behind them, and the visual guidelines (colors, typography, layout) needed to implement them consistently, as well as technical instructions to ensure the components worked properly (minimum recommended width/height, minimum font size, etc).

This structure was built so the team could keep developing and iterating without us in the room.

Return Home
×
Manage Consent
To provide the best experiences, we use technologies like cookies to store and/or access device information. Consenting to these technologies will allow us to process data such as browsing behavior or unique IDs on this site. Not consenting or withdrawing consent, may adversely affect certain features and functions.
Functional Always active
The technical storage or access is strictly necessary for the legitimate purpose of enabling the use of a specific service explicitly requested by the subscriber or user, or for the sole purpose of carrying out the transmission of a communication over an electronic communications network.
Preferences
The technical storage or access is necessary for the legitimate purpose of storing preferences that are not requested by the subscriber or user.
Statistics
The technical storage or access that is used exclusively for statistical purposes. The technical storage or access that is used exclusively for anonymous statistical purposes. Without a subpoena, voluntary compliance on the part of your Internet Service Provider, or additional records from a third party, information stored or retrieved for this purpose alone cannot usually be used to identify you.
Marketing
The technical storage or access is required to create user profiles to send advertising, or to track the user on a website or across several websites for similar marketing purposes.
  • Manage options
  • Manage services
  • Manage {vendor_count} vendors
  • Read more about these purposes
View preferences
  • {title}
  • {title}
  • {title}