Skip to main content

Public Mobility B2C Mobile & B2B Operations Design System

Smart Ticket: Mobile Ticketing & Transit Operations

My Role
2022 - 23: UX/UI Designer · 2026: Senior Product Designer
Team
2022 - 23: UX/UI Designer (me), 2 Product Owners, Business Analyst, mobile development team · 2026: solo redesign
Timeline
Q4 2022 - May 2023: original concept · 2026: full system rebuild
Platform
iOS & Android passenger app · responsive web operations console
Key Outcome
Redesigned the 2022 transit concept in Figma: created a tokenised WCAG 2.2 design system, designed offline ticketing flows, and framed a municipal operations console.

Executive Summary

Ticketing apps usually fail riders at the worst moment.

The Problem

Riders buy tickets while running for a tram, underground without signal, or unsure which zone they need. A slow checkout, a ticket that will not load during an inspection, or the wrong fare can each end in a missed ride or a fine. The 2022 concept followed the initial business brief: hard-coded styles, instant activation and a manual admin model.

My Part

In 2022 - 23 I was the UX/UI designer next to 2 product owners, a business analyst and the mobile developers: I reviewed the requirements, removed dark patterns and delivered the personas, user flows, style guide and mockups. In 2026 I rebuilt the system alone in Figma: a token-based design system, 56 mobile screens and states and 8 operations console screens. The original 2022 screens stay in the file for comparison.

Users

Three Riders, Each with a Moment of Stress

Each persona is based on the 2022 research and points to one design decision. Every rider signs in or creates an account first - the app has no guest mode.

  • Tomasz, 34

    Daily office commuter

    • Metro M1
    • Tram 17

    Role & Context

    Commutes every day by metro and tram between home and the business district. Travels in the morning and afternoon peak.

    Main Goal

    Catch tight connections without checking several apps, and show his ticket quickly when an inspector checks.

    Everyday Problems

    • Traffic jams: He worries that his 20-minute ticket will run out before his stop.
    • No signal underground: Mobile internet drops, so slow ticket apps fail during a ticket check.
    • Invoices: He forgets to download PDF invoices for his monthly company expense report.

    How Smart Ticket Helps

    • Live Activity: The Lock Screen shows journey progress and the arrival time in minutes.
    • Offline QR pass: The pass works without mobile signal in the metro.
    • One-tap invoice: “Download PDF Invoice” sits on the receipt screen.
  • Zuzanna, 21

    University student

    • Bus 131
    • Tram 4

    Role & Context

    Uses buses, trams and night routes across the city. Has a small student budget and switches between single rides and day passes.

    Main Goal

    Buy a discounted student ticket fast, without paying full price by mistake or getting a fine.

    Everyday Problems

    • Fare mix-ups: In a hurry, she mixes up Standard and Reduced (-50%) fares.
    • Diversions: Route diversions and track repairs make her miss classes.
    • Declined cards: Her card is sometimes declined just before boarding.

    How Smart Ticket Helps

    • Clear fare toggle: A “Standard / Reduced -50%” toggle sits at the top of the ticket sheet.
    • Live status: The Schedules screen shows saved lines with live status (“Delayed +4 min”) and service alerts such as “Tram line 4 route diverted”.
    • Quick payment: She pays with a 6-digit BLIK code, Apple Pay or the Smart Wallet - no card number to type.
  • Elena & Marco, 29

    Weekend tourists

    • Metro M2
    • Tram 9

    Role & Context

    Visiting Warsaw for a 3-day city trip. They do not speak Polish and have never used the local transit network.

    Main Goal

    Travel from the central station to the sights without learning the zone and ticket rules.

    Everyday Problems

    • Unknown fares: They do not know which ticket (20-minute, 75-minute, 90-minute or 24-hour; Zone 1 or Zones 1+2) covers their trip.
    • New account: Before the first ride they must set up an account in an app they have never used.
    • Hard stop names: They miss their stop because Polish stop names are hard to read and remember.

    How Smart Ticket Helps

    • Ticket in the result: Route results show the ticket that covers the trip, with its price and a “Select & Buy” button.
    • Start on board: They buy in advance and start the ticket by scanning the QR code in the vehicle.
    • Step-by-step route: Route details list each leg, transfer walk and stop count, with live arrival times.

User Flow

From Trip Search to an Offline Inspection

The main path has one rule: buying and activating are separate steps. A rider can buy at home, keep the pass inactive, and start the countdown only when the vehicle arrives.

Design System

Tokens That Make Accessibility Testable

  • Three Tiers, One Source of Truth

    Primitives (hidden from publishing) feed semantic tokens with Light and Dark mode, plus dimension and effect collections. Components reference semantic tokens only, so a theme change happens in one place.

    All 175 variables carry CSS code syntax. The handoff page specifies a W3C DTCG JSON export (one file per mode) and maps each token to CSS, Tailwind and React Native.

  • Contrast You Can Check

    Brand indigo #4338CA reaches 7.9:1 on white - WCAG 2.2 AAA. Twelve token pairs are checked in both modes, with ratios computed from the live variables: all text pairs pass AA and both border pairs pass 3:1. In Dark mode the brand role steps to brand/400 (5.8:1).

    Solid status fills use the 700 steps (#047857, #B91C1C), so white labels pass AA (5.5:1 and 6.5:1), and ticket status is never shown by colour alone.

  • Tonal Surfaces, Multi-Tenant Ready

    Cool slate neutrals (slate/0 to slate/950) group content by background instead of heavy borders, and every text tier stays at 4.5:1 or more (the lowest, text/muted, is 4.9:1).

    A tenant variable collection (Warsaw ZTM, Berlin VBB, Prague PID) drives city names across the console; per-city currency and data are the next step.

2022 Brief vs 2026 Rebuild

From an Exploratory Prototype to a Production-Ready System

The 2022 concept followed the initial business brief: manual operational inputs, instant activation on purchase and decorative brand styling. That was the right scope for a prototype meant to win client approval. In 2026 I tested the same ideas against current standards - WCAG 2.2, W3C Design Tokens (DTCG), GDPR privacy by design and European transit data protocols (GTFS-RT, SIRI-SX, NeTEx) - and changed what did not hold up.

Visual Foundation: From Decorative Styling to Tokens

2022 Brief · Initial Assumption

The brief asked for a decorative brand look. Colours were hard-coded hex values. The brand blue #204796 passed (8.7:1), but placeholder grey #A3A3A3 reached 2.5:1, and the disabled button (#CCCCCC with a white label) 1.6:1.

  • 2022 - Sign up by phone number
  • 2022 - Sign up by email

2026 Decision

Every colour is a token with values for Light and Dark mode. Primary #4338CA reaches 7.9:1 on white. Cool slate neutrals and soft elevation replace one-off greys, so dense lists stay easy to scan.

  • Create account / Details - Light mode
  • Create account / Details - Dark mode

Why - The Standard

  • WCAG 2.2 SC 1.4.3: At least 4.5:1 for body text and tags.
  • Outdoor CTAs: Primary button labels reach 7.9:1 in Light mode (the WCAG AAA level, SC 1.4.6), because riders read screens in direct sunlight.
  • W3C DTCG: One token format, so the same values reach iOS, Android and web without manual copying.

Evidence on the Canvas

  • Contrast: brand/primary #4338CA reaches 7.9:1 on white; text/muted 4.9:1; status text on status backgrounds 6.8 to 7.6:1.
  • Variables: 175 variables in 5 collections, with Light and Dark mode.
  • Handoff: The Token Handoff page documents the DTCG JSON export: one file per mode.

Profile and Security

Mostly readable in 2022, but every colour was a one-off value that could not support Dark mode.

Legacy Concept (2022)

Most text passed, but grey helper text on the security screen reached only 2.5:1. None of the colours were linked to a system, so one change meant editing every screen.

  • 0% of colours from tokens
  • 3 text contrast failures
  • Lowest text 2.5:1
  • 2022 - Security
  • 2022 - My Profile

Modern Rebuild (2026)

Same content, rebuilt from tokens and components (List / Menu Row, Avatar). Biometrics, password and sign-out sit in one predictable list.

  • 100% of colours from tokens
  • 0 text contrast failures
  • Lowest text 4.9:1
  • Profile / Main Hub
  • Profile / Security & Biometrics

Passenger App

Designed for the Moments That Usually Go Wrong

Each feature answers a real edge case of riding public transport: no signal underground, a ticket that starts too early, unclear fares and a payment that must be quick.

  • Offline QR Pass

    The pass is stored on the phone and says so: “No internet connection • Your ticket is safely stored offline”. It shows a live countdown and a QR code an inspector can scan without a network - the main fear riders have in the metro. The design specifies a signed token for offline checks; signing itself is an engineering requirement, outside the design scope.

  • Buy Now, Start Later

    Buying and activating are separate steps. Riders buy ahead, and the timer starts only when they scan the QR code opposite the vehicle door, or at the station before the metro gates. If the code can’t be scanned, they type the vehicle side number.

  • From Route to Ticket in 3 Taps

    Every route result already shows the ticket that covers the trip, for example a 20-minute ticket for PLN 4.40. “Select & Buy” opens one sheet with a Standard / Reduced -50% toggle that marks the ticket covering the trip, and riders can still pick another. “Continue to payment” and “Pay” finish the purchase.

  • Fast Payment, One Sheet

    Checkout is one “Review & Pay” sheet with the Smart Wallet, Apple Pay and BLIK. BLIK opens a 6-digit code entry with a visible expiry timer, so riders always know the code is still valid.

  • The Journey on the Lock Screen

    During the trip, an iOS Live Activity shows progress between stops and the minutes to arrival, with a shortcut straight to the inspection QR code.

B2B Operations

Run the Network (Operations Console)

The operations console serves the transit staff who run the network. Real-time feeds replace manual entry, fleet and validators are monitored live, tariffs are published to the app and validators, and every sensitive action is logged.

Design Decisions

  • Feeds: GTFS-RT and SIRI-SX for live data, NeTEx / GTFS for static timetables.
  • Fleet: 1,248 vehicles across 4 operators on one ZTM network; validators sync every 60 s.
  • Privacy by design: Browsing passenger accounts is disabled; staff open one masked record by exact reference, and access expires after 15 minutes.
  • Governance: An append-only audit log, retained for 7 years.
  • Admin / Operations Dashboard
  • Admin / Automated Transit Feeds & Alerts Engine
  • Admin / Fleet & Vehicle Management
  • Admin / Multi-Operator Fleet & Clearing Registry
  • Admin / Fare & Tariff Configuration
  • Admin / Access Control & Team Permissions
  • Admin / Security Audit Trail & Logs
  • Admin / Application Security & Policies

Outcomes

What the Redesign Delivers

  • 2 products, 1 system

    56 mobile screens and states and 8 operations console screens share 175 variables in 5 collections.

  • WCAG 2.2 AA

    12 token pairs checked in Light and Dark mode all pass AA, or 3:1 for non-text; primary indigo reaches AAA (7.9:1) in Light mode.

  • 3 taps

    From a route result to a ticket paid from the wallet: Select & Buy → Continue to payment → Pay. BLIK adds its code.

  • No passenger browsing

    Staff cannot browse passenger accounts; one masked record opens by exact reference and is logged.

  • Offline inspection

    The active pass and its QR code are designed to show without a network connection.

  • Real data standards

    GTFS-RT, SIRI-SX and NeTEx / GTFS feeds replace manual timetable and alert inputs.

This is a concept redesign: the outcomes describe verified design decisions, not production metrics.

Lessons Learned

What I Would Tell My 2022 Self

  • UX Belongs in the Requirements

    Most 2022 problems were written into the specification before any design work. Reviewing requirements early is still the cheapest fix.

  • Tokens Make Quality Measurable

    With semantic tokens, contrast and Dark mode become checks you can run, not opinions to defend.

  • Use the Data the City Already Has

    Designing around GTFS, SIRI and operator contracts made the operations console simpler and more honest than inventing manual workflows.