UX/UI Design

UX/UI design for
complex products,
not decorative screens.

Devlopa designs interfaces through research, systems thinking, prototyping, and evidence-based iteration. Every design decision is connected to user behavior, technical constraints, business goals, and product risk.

Start a UX Engagement

Our UX process

Nine stages. Evidence at every step.

01

Discover

Stakeholder interviews, context mapping, and defining what success looks like for the product and its users.

02

Research

User interviews, task analysis, workflow observation, competitive review, and cognitive load assessment.

03

Map

FigJam journey maps, service blueprints, system maps, and information priority mapping, making the invisible visible.

04

Ideate

Sketch multiple layout models, compare tradeoffs, and converge on a design direction with stakeholder input.

05

Structure

Information architecture, content hierarchy, navigation design, and component inventory.

06

Prototype

High-fidelity Figma prototypes with interactive states, design system tokens, and responsive variants.

07

Test

Scenario-based usability tests, error rate measurement, confidence calibration, and synthesis of findings.

08

Handoff

Developer-ready Figma files, design tokens, component documentation, and handoff notes.

09

Iterate

Post-launch feedback loops, A/B testing collaboration, and continuous design improvement.

Tools & methods

FigmaFigJamDesign tokensComponent librariesUser journey mapsService blueprintsWireframesInteractive prototypesUsability test scriptsAccessibility auditsDeveloper handoff docsStorybook integration

Representative case studies

Five fully developed UX engagements.

These are representative case studies based on real UX engagement patterns. Each shows full research-to-handoff detail.

Public Safety & Infrastructure Operations

Geospatial Intelligence Command Platform

High-stakes interface design for geospatial event monitoring.

The Problem

Operators needed to monitor geospatial events, satellite-derived indicators, sensor feeds, field reports, and risk zones in one interface. Existing workflows required switching between GIS tools, spreadsheets, message threads, and static reports, creating cognitive overload and delayed decisions.

User Research Findings

  • Cognitive load assessment revealed layer overload reduced decision speed by 40%
  • Task analysis showed analysts switched tools 12+ times per investigation
  • Time-critical decision points required sub-30-second triage capability
  • Color-coding misuse created false urgency in 3 of 5 test scenarios

Users

Geospatial analystsOperations leadsField coordinatorsRisk officersData scientistsExecutive decision makers

Key Design Decisions

  • Progressive disclosure to prevent map overload at initial load
  • Separated observation, analysis, and recommendation layers to reduce confirmation bias
  • Confidence indicators on all model-derived insights with source timestamps
  • Spatial clustering at low zoom to prevent visual noise
  • Temporal scrubber for change detection across time ranges
  • Audit trail for all analyst decisions and escalations
  • Accessibility for color-blind users and low-light command environments

Delivery Phases

01Stakeholder interviews
02Task analysis & GIS workflow review
03FigJam system map & journey map
04Ideation (4 layout models compared)
05Figma prototype (9 screens)
06Scenario-based usability testing
07Developer handoff & design system
FigJamFigmaUsability TestingDesign SystemAccessibilityGeospatial UX

Figma Prototype Screens

Command overviewEvent detail drawerLayer managerTime-series analysisEvidence comparisonAnalyst notesExecutive report exportCollaboration handoffMobile field summary
Financial Risk Operations Team

Fintech Risk Monitoring Dashboard

Precision risk interface with audit-grade decision traceability.

The Problem

Risk analysts needed to identify suspicious activity, monitor financial exposure, and escalate cases quickly, across multiple data sources with strict audit requirements.

User Research Findings

  • Analysts scanned 200+ alerts per shift, prioritization was the core problem
  • Alert fatigue led to escalation delays averaging 47 minutes
  • Compliance required every decision to have a documented rationale

Users

Risk analystsCompliance officersOperations managers

Key Design Decisions

  • Alert triage interface with severity hierarchy and smart grouping
  • Entity profile drawers with cross-referenced transaction history
  • Audit trail visible at every decision point
  • Escalation workflow with mandatory documentation fields
  • Color system based on severity, not category, reducing misclassification

Delivery Phases

01Compliance & analyst interviews
02FigJam risk workflow map
03Alert prioritization ideation
04Figma prototype
05Scenario-based usability testing
06Developer handoff
Risk UXFigmaAudit Trail DesignInformation HierarchyCompliance
Regional Healthcare Provider

Healthcare Patient Intake System

Accessible, form-forward intake design for diverse patient populations.

The Problem

Patient onboarding was slow, repetitive, and confusing, especially for elderly users, non-native speakers, and patients with low digital literacy.

User Research Findings

  • Form abandonment occurred most often on step 3 of 6, medical history
  • 29% of patients needed admin help to complete digital intake
  • Plain language reduced re-read rates by estimated 40% in prototype testing

Users

Patients (all demographics)Admin staffClinicians

Key Design Decisions

  • Multi-step intake with progress indicators and save-and-return
  • Plain language throughout, no medical jargon in patient-facing screens
  • Accessible first, WCAG 2.1 AA, keyboard-navigable, screen reader tested
  • Mobile-first layout, 64% of patients accessed via smartphone
  • Clear error recovery with specific, actionable messages

Delivery Phases

01Patient & staff interviews
02FigJam service blueprint
03Form fatigue ideation
04Figma prototype
05Usability testing (diverse user group)
06Developer handoff
Healthcare UXAccessibilityForm DesignMobile-firstPlain Language
D2C Consumer Brand

E-commerce Personalization Experience

Reducing discovery friction and improving conversion through design.

The Problem

Customers struggled to find relevant products and abandoned shopping journeys, even when the product they needed was in stock.

User Research Findings

  • Search-to-purchase conversion was 40% below industry average
  • Customers compared 5+ products before purchasing, no comparison tool existed
  • Wishlist abandonment correlated with checkout complexity, not price

Users

Returning customersFirst-time visitorsMobile shoppers

Key Design Decisions

  • Personalized homepage with progressive personalization, no account required
  • Product comparison drawer with side-by-side specifications
  • Streamlined checkout with one-click return for saved addresses
  • Performance-aware design, images lazy-loaded, animations disabled on slow connections

Delivery Phases

01Customer segment research
02FigJam journey map
03Recommendation surface ideation
04Figma prototype
05Findability & conversion testing
06Developer handoff
E-commerce UXPersonalizationConversion OptimizationPerformance UX
Enterprise Logistics Operator

Logistics Fleet Operations Interface

Operational clarity for dispatchers managing time-critical fleet events.

The Problem

Operations teams needed better visibility into vehicles, drivers, shipments, exceptions, and delays, but existing tools were slow, cluttered, and required too many clicks for time-critical decisions.

User Research Findings

  • Dispatchers made 30+ decisions per hour, UI latency created cascading delays
  • Exception alerts were buried in general notifications, critical events missed
  • Map vs table debate: dispatchers preferred map, managers preferred list, solution: both

Users

DispatchersOperations managersFleet supervisors

Key Design Decisions

  • Split-view interface: fleet map + sortable shipment list
  • Exception queue as first-class UI element, always visible
  • Driver detail panel with ETA timeline and contact action
  • Role-based views: dispatcher mode vs manager mode
  • Reduced cognitive load through alert hierarchy and visual scanning patterns

Delivery Phases

01Dispatcher & manager interviews
02FigJam operational workflow map
03Map vs table ideation
04Figma prototype
05Time-critical dispatch testing
06Developer handoff
Logistics UXOperational InterfaceRole-based DesignMap UIFigma

Need a UX partner who goes beyond screens?

We run structured research, map real workflows, prototype with rigor, and hand off Figma files your engineers can actually build from.