Live Preview (Coming Soon)

Eco-Addis Mobile — Super App for Addis Ababa

Title

Eco-Addis — A super-app for e-commerce, food delivery and ride-hailing in Addis Ababa

My Role

Lead UX/UI Designer

Team

1 Product Manager, 1 UI Designer, 1 UX Researcher, 2 Developers

Timeline

5 Months

Project Type

Personal / Client

Tools Used

Figma, FigJam, Google Forms, Maze

Problem Statement

Addis Ababa's rapidly growing urban population faces fragmented digital commerce experiences — separate apps for shopping, food delivery, and transportation. Vendors lack affordable digital storefronts, while consumers juggle multiple platforms with inconsistent UX. Eco-Addis was designed to solve this with a single, unified super-app ecosystem tailored specifically to Addis Ababa's urban lifestyle — supporting Ethiopian Birr (ETB), Amharic context, and local business categories.

Users & Pain Points

Who are the users?

Urban Addis Ababa residents aged 18–40 — students, professionals, and small business owners who are mobile-first consumers.

What are their goals?

Shop for products, food, and services in one place|Find nearby restaurants and get food delivered quickly|Order affordable rides without switching apps|Sell products or run a vendor shop digitally|Discover local businesses through video and stories

Pain points

No single app serving e-commerce, food delivery, and rides in the Ethiopian market|Existing global apps (Jumia, Uber) lack local language support and local business inventory|Small vendors have no accessible digital storefront|Currency and payment flows are not localized (no ETB, no local delivery logic)|Distrust of complicated onboarding — users drop off before first purchase

Disputes over draw fairness — no verifiable random selection

No single place to view contribution history, remaining rounds, or upcoming draws

Organizers overwhelmed managing payments and member communications manually

No formal way to submit a cancellation or special request

No single app serving e-commerce, food delivery, and rides in the Ethiopian market|Existing global apps (Jumia, Uber) lack local language support and local business inventory|Small vendors have no accessible digital storefront|Currency and payment flows are not localized (no ETB, no local delivery logic)|Distrust of complicated onboarding — users drop off before first purchase

"I want to see my payment history and the draw results in one place — not scroll through a WhatsApp group."

Process & Methods

Goals

Understand how Addis Ababa residents currently shop, eat, and travel — and where digital tools fail them

Methods

User interviews with Addis residents across income groups|Competitor analysis: Jumia Ethiopia, ride apps, informal WhatsApp commerce|Card sorting to determine navigation structure for a multi-service app|Contextual inquiry at local markets and food spots (Bole, Saris, Merkato)

Key Findings & Insights

Users strongly prefer a single app over switching — super-app model validated|ETB pricing and Amharic map labels are trust signals, not just nice-to-haves|Flash deals and time-limited offers drive impulse purchases in food delivery|Vendors want easy onboarding — category/subcategory industry selection must be simple|Social features (stories, video Watch tab) increase time-in-app and discovery|Ride-hailing users want saved frequent destinations and trip history at a glance

Final Solution

A clean locally-rooted mobile super-app with five core verticals: Market Place (product discovery, vendor shops, wishlist, reviews, flash deals); Food Delivery (restaurant pages, special offers, basket, checkout, order tracking); Eco Ride (map-based ride ordering, delivery mode, trip history, Eco Miles loyalty); Watch (vertical video feed for business promotion and discovery); and Me (user profile, my products, wallet, shop management, referrals). Design uses amber/golden yellow primary, dark navy secondary, ETB currency throughout, and real Addis Ababa addresses and Amharic map context.

Impact / Results

Onboarding completion rate target: >80%|Time to first order target: <3 minutes|Task success rate (find and add item to cart) target: >90%|Vendor registration completion target: >70%|SUS Score target: >80

Lessons Learned

Designing a super-app requires ruthless information architecture — the hardest challenge was keeping five product verticals discoverable without overwhelming the home screen|Localization is a UX feature not an afterthought — real Addis Ababa streets, ETB pricing, and Ethiopian food context in banners built immediate trust|Social commerce is underutilized in African markets — the Watch tab and Stories features were strong discovery and retention mechanisms|Vendors are users too — the vendor registration and boost flows needed as much design care as the consumer-facing shopping experience

Beyond (Soon)

© 2026 Nahom Girma. Designed & Hosted with 🦾 on

Live Preview (Coming Soon)

Eco-Addis Mobile — Super App for Addis Ababa

Title

Eco-Addis — A super-app for e-commerce, food delivery and ride-hailing in Addis Ababa

My Role

Lead UX/UI Designer

Team

1 Product Manager, 1 UI Designer, 1 UX Researcher, 2 Developers

Timeline

5 Months

Project Type

Personal / Client

Tools Used

Figma, FigJam, Google Forms, Maze

Problem Statement

Addis Ababa's rapidly growing urban population faces fragmented digital commerce experiences — separate apps for shopping, food delivery, and transportation. Vendors lack affordable digital storefronts, while consumers juggle multiple platforms with inconsistent UX. Eco-Addis was designed to solve this with a single, unified super-app ecosystem tailored specifically to Addis Ababa's urban lifestyle — supporting Ethiopian Birr (ETB), Amharic context, and local business categories.

Users & Pain Points

Who are the users?

Urban Addis Ababa residents aged 18–40 — students, professionals, and small business owners who are mobile-first consumers.

What are their goals?

Shop for products, food, and services in one place|Find nearby restaurants and get food delivered quickly|Order affordable rides without switching apps|Sell products or run a vendor shop digitally|Discover local businesses through video and stories

Pain points

No single app serving e-commerce, food delivery, and rides in the Ethiopian market|Existing global apps (Jumia, Uber) lack local language support and local business inventory|Small vendors have no accessible digital storefront|Currency and payment flows are not localized (no ETB, no local delivery logic)|Distrust of complicated onboarding — users drop off before first purchase

Disputes over draw fairness — no verifiable random selection

No single place to view contribution history, remaining rounds, or upcoming draws

Organizers overwhelmed managing payments and member communications manually

No formal way to submit a cancellation or special request

No single app serving e-commerce, food delivery, and rides in the Ethiopian market|Existing global apps (Jumia, Uber) lack local language support and local business inventory|Small vendors have no accessible digital storefront|Currency and payment flows are not localized (no ETB, no local delivery logic)|Distrust of complicated onboarding — users drop off before first purchase

"I want to see my payment history and the draw results in one place — not scroll through a WhatsApp group."

Process & Methods

Goals

Understand how Addis Ababa residents currently shop, eat, and travel — and where digital tools fail them

Methods

User interviews with Addis residents across income groups|Competitor analysis: Jumia Ethiopia, ride apps, informal WhatsApp commerce|Card sorting to determine navigation structure for a multi-service app|Contextual inquiry at local markets and food spots (Bole, Saris, Merkato)

Key Findings & Insights

Users strongly prefer a single app over switching — super-app model validated|ETB pricing and Amharic map labels are trust signals, not just nice-to-haves|Flash deals and time-limited offers drive impulse purchases in food delivery|Vendors want easy onboarding — category/subcategory industry selection must be simple|Social features (stories, video Watch tab) increase time-in-app and discovery|Ride-hailing users want saved frequent destinations and trip history at a glance

Final Solution

A clean locally-rooted mobile super-app with five core verticals: Market Place (product discovery, vendor shops, wishlist, reviews, flash deals); Food Delivery (restaurant pages, special offers, basket, checkout, order tracking); Eco Ride (map-based ride ordering, delivery mode, trip history, Eco Miles loyalty); Watch (vertical video feed for business promotion and discovery); and Me (user profile, my products, wallet, shop management, referrals). Design uses amber/golden yellow primary, dark navy secondary, ETB currency throughout, and real Addis Ababa addresses and Amharic map context.

Impact / Results

Onboarding completion rate target: >80%|Time to first order target: <3 minutes|Task success rate (find and add item to cart) target: >90%|Vendor registration completion target: >70%|SUS Score target: >80

Lessons Learned

Designing a super-app requires ruthless information architecture — the hardest challenge was keeping five product verticals discoverable without overwhelming the home screen|Localization is a UX feature not an afterthought — real Addis Ababa streets, ETB pricing, and Ethiopian food context in banners built immediate trust|Social commerce is underutilized in African markets — the Watch tab and Stories features were strong discovery and retention mechanisms|Vendors are users too — the vendor registration and boost flows needed as much design care as the consumer-facing shopping experience

Beyond (Soon)

© 2026 Nahom Girma. Designed & Hosted with 🦾 on

Live Preview (Coming Soon)

E-LMIS — Digital Court System

Title

E-LMIS — Labor Relation Board Digital Court Systemt

My Role

Lead UI/UX Designer

Team

Nahom Girma (Designer)

Timeline

5 Weeks

Project Type

Government / Enterprise

Tools Used

Figma

Problem Statement

Ethiopia's Labor Relation Board handles labor disputes between workers, employers, and organizations — a process historically reliant on paper-based case files, manual scheduling, in-person hearings, and fragmented communication between courts, registrars, chairmen, judges, and plaintiffs. This created: slow case intake with paper forms and manual review; lack of transparency with plaintiffs having no visibility into case status; hearing coordination bottlenecks with scheduling and judge assignment done ad hoc; no audit trail for hearing minutes and decisions; and access barriers requiring physical presence at every stage. The challenge was to design a unified digital court platform that digitalizes the entire case lifecycle — from filing to final decision — while accommodating five distinct user roles with different permissions and workflows.

Users & Pain Points

Who are the users?

Five distinct roles: Plaintiff (files new labor cases, uploads documents, tracks case progress), Registrar (receives new cases, reviews submissions, approves or declines intake), Chairman (oversees approved cases, assigns judges, routes cases to mediation), Judge (manages hearing schedule, conducts live hearings, issues decisions), and Court Digital Expert (observes all live hearing sessions, ensures digital recording integrity).

What are their goals?

Plaintiffs: file cases digitally and track progress in real time|Registrars: review and process incoming cases efficiently|Chairmen: assign judges and generate official bilingual summons|Judges: conduct live hearings with real-time minute-taking and issue decisions|Government: maintain audit trail and oversight of all labor dispute proceedings

Pain points

Slow case intake due to paper forms and manual review|Plaintiffs had no visibility into case status|Hearing scheduling and judge assignment done ad hoc|No audit trail for hearing minutes, decisions, and document exchanges|Physical presence required at every stage of the process

Disputes over draw fairness — no verifiable random selection

No single place to view contribution history, remaining rounds, or upcoming draws

Organizers overwhelmed managing payments and member communications manually

No formal way to submit a cancellation or special request

Slow case intake due to paper forms and manual review|Plaintiffs had no visibility into case status|Hearing scheduling and judge assignment done ad hoc|No audit trail for hearing minutes, decisions, and document exchanges|Physical presence required at every stage of the process

"I want to see my payment history and the draw results in one place — not scroll through a WhatsApp group."

Process & Methods

Goals

Digitize the full labor dispute lifecycle end-to-end on a single platform|Design role-based access where each user type sees only what is relevant to their function|Enable real-time hearing support with live minute-taking|Provide official system-generated bilingual (English + Amharic) legal summons

Methods

Stakeholder analysis of Ministry of Labor and Skills court workflows|Multi-role process mapping for 5 user types across case lifecycle|Review of existing paper-based court procedures and documentation|Analysis of E-LMIS ecosystem for integration requirements

Key Findings & Insights

Each of the 5 roles requires a unique dashboard and permission set — a one-size-fits-all dashboard would bury critical role-specific actions|Live hearing sessions require unmistakable active-state awareness (red border and Live Now badge)|Legal documents in Ethiopia must be in Amharic — automating this removes a critical manual step and ensures compliance|The split-panel case view eliminates constant back-and-forth between case details and documents|Double-confirmation for mediation closure is essential since mediation is legally binding and irreversible

Final Solution

A role-based digital court platform (20+ screens, 5 user roles) with: role-specific dashboards with KPIs and analytics; a split-panel case view keeping case details and documents simultaneously visible; automatic generation of bilingual (English + Amharic) legal summons as PDF; a live hearing session interface with red-border active state, real-time minute log, and session controls; a weekly calendar view for docket management; and a mediation flow with double-confirmation for irreversible actions.

Impact / Results

20+ screens across 5 user roles delivered|Bilingual (English + Amharic) automated summons generation|Case lifecycle fully digitized from filing to decision

Lessons Learned

The role-based architecture is thorough — every screen is correctly scoped to its user avoiding both information overload and permission ambiguity|The live hearing session design is a standout interaction: the red border, Live Now badge, real-time minute log, and session controls make an unprecedented interface feel immediately understandable|Bilingual document generation (Amharic summons) is the strongest case for a custom-designed system — no off-the-shelf tool provides this|Color-coded status system is consistent and scannable across all roles and views|The Redesign Exploration (lighter sidebar-free UI) merits further testing as a direction toward a more modern SaaS aesthetic

Beyond (Soon)

© 2026 Nahom Girma. Designed & Hosted with 🦾 on