All work
GovTechDesign systemWeb and mobile2025–2026

E-Government Gateway

Rebuilding Lithuania's national public services portal from the ground up, and shaping its mobile app, around life events instead of institutions.

One structure for web and mobile: find a service by life event, then follow every order.

Visit epaslaugos.lt

My role Senior UX designer, web and mobile
Team State Digital Solutions Agency (VSSA) product and engineering teams
Timeline 15 months, 2025–2026
Platform Web portal and native mobile app

At a glance

01 Problem

A 20-year-old portal could no longer carry a country's public services.

GoalMake public services findable by what people need, not by which agency owns them.

Challenge

Built nearly 20 years ago, the legacy portal was slow and technically outdated, and its experience had not kept pace with its scale. It needed a ground-up rebuild, re-architected so one failure could not take everything down.

Outcome

The rebuilt portal carries national-scale traffic: 28,131 daily logins, 23.5M logins and 21M+ services ordered this year. Daily logins are up 35% since the update.

Business Thousands of services across dozens of institutions had to feel like one product
Usability People arrive with a situation, not an agency name, yet the old structure expected them to know who handles it
Engineering A 20-year-old foundation was slow and fragile, so the rebuild had to be modular and contain partial failures

Elektroniniai valdžios vartai (epaslaugos.lt) is Lithuania's central portal for public e-services, run by the State Digital Solutions Agency. It connects citizens and businesses with dozens of institutions, from a young parent declaring a birth to a company applying for a permit.

02 Users

From a young parent declaring a birth to a business applying for a permit.

C
Citizen with a life event Arrives with a situation, such as a new child
Business Wants the right service without knowing which agency owns it
Usability Needs documents, cost and duration upfront
Tech Moves between web and mobile and expects the same structure
B
Business applying for a permit Handles regulatory services across several institutions.
Business Needs services from different providers in one place
Usability Narrows results by provider, price and audience
Tech Tracks several orders and their statuses
R
Returning user Already knows the type of service and wants the shortest route.
Business Wants a direct route to a known service
Usability Browses by category or searches
Tech Relies on saved services and order history in Mano

03 Process

One structure for web and mobile, built on a new design system.

01 Design system 4 months
02 Web portal 8 months
03 Mobile app 7 months
UX & UI design me Design system me Product and engineering VSSA teams
Finding a service
4 steps
  1. 01 Arrive with a need GoalFind the right service FrictionNavigation follows institutions, so you must know the agency
  2. 02 Search GoalNarrow down hundreds of services FrictionResults without meaningful filters
  3. 03 Open a service GoalUnderstand what is required FrictionDocuments, cost and duration mixed into dense text
  4. 04 Order GoalStart the request FrictionLittle sense of what happens next

The old structure mirrored the institutions, not the people using them.

New web portal
5 steps
  1. 01 Arrive GoalLife events or categories, two parallel entry points
  2. 02 Narrow down GoalFilter by category, provider, life event, price, audience
  3. 03 Read the service page GoalTabs for description, process and more info; documents, cost, duration
  4. 04 Order GoalA direct order action on the page
  5. 05 Stay informed GoalNotifications scoped to your own life events

Everything a person needs to decide is on one page.

Mobile app
5 steps
  1. 01 Open the app GoalLife events first, with a switch to categories
  2. 02 Read a service GoalCollapsible sections for description, documents and cost
  3. 03 Order GoalA persistent order button
  4. 04 Track in Mano GoalOngoing, completed, rejected and saved services in one place
  5. 05 Control updates GoalPer-life-event toggles and channels

The app mirrors the web structure, so citizens do not relearn it.

Order statuses
4 steps
  1. 01 Ordered GoalRequest received (Užsakyta)
  2. 02 Pending GoalWaiting for the provider (Laukiama)
  3. 03 Under review GoalBeing handled (Nagrinėjama)
  4. 04 Completed GoalDone (Įvykdyta)
Information architecture One structure for web and mobile, built on shared logic: life events, categories and services.
Design system Foundations, components and patterns shared by the web portal and the mobile app.

04 Decisions

Two ways in, so first-timers and regulars both find their way.

  • Life events first, categories alongside People arrive with a situation, while regulars still want direct category access CostTwo navigation models to keep consistent
  • A rebuild, not a reskin A 20-year-old foundation could not be fixed from the surface CostA long programme without a quick visible win
  • Modular, resilient architecture If one part fails, citizens still reach essential services CostMore integration work between modules
  • Service pages with documents, cost and duration upfront People know what to expect before they start CostDense information needs a strict hierarchy
  • Notifications scoped to life events A blanket subscription sends irrelevant updates CostMore settings to design and explain
  • One structure for web and mobile Citizens move between the two without relearning CostThe app must stay in step with every web change

05 Solution

Services organised around life events, not institutions.

  • Life-event-first navigation: services organised around real situations, not institutional silos
  • Dual entry points: life events and service categories side by side
  • Structured, filterable search: faceted filters and clear tagging across hundreds of listings
  • Transparent service pages: description, process, documents and cost clearly separated
  • Granular personalisation: notifications scoped to specific life events
  • Trust and accessibility: EU and ISO trust badges, accessibility toggle, LT and EN
scroll
An entry point built around intent

The portal now opens on what people need: life events, service categories and live platform activity in one orienting view, instead of an institutional map.

scroll
Structure for hundreds of services

Faceted filters narrow the catalogue by provider, cost, audience and life context, while categories stay as a second path for people who know what they want.

scroll
A legible, actionable service page

Description, process and requirements are separated, so a dense bureaucratic listing becomes clear: what is needed, what it costs, how long it takes.

scroll
Control over what reaches you

Notification and reminder preferences are tied to individual life events, instead of a single blanket subscription.

scroll
The same structure in your pocket

Life events lead, and Mano consolidates ongoing, completed, rejected and saved services, payments and documents in one place.

scroll
Every request, at a glance

Each order shows its stage, ID, timestamps and provider contacts, with documents available to download.

Before
After
Before After

The portal homepage before and after the rebuild.

06 Results

The rebuilt platform carries national-scale traffic.

28,131 Daily logins up 35% since the update
3,700 services ordered every day. portal statistics
3.5M Logins this year portal statistics

Portal live statistics, 2026. The 35% compares 2024-2025 before and after launch.

What I would do differently

A rebuild at national scale is a product programme, not a visual refresh. Two ways in beat one clever one: people with a situation and people with a destination both need a path.