SELECTED WORK

Three projects. One way of working.

One case study that goes all the way down, and two more shown as the interfaces they are. Every one of them started from a problem somebody actually has.

THE PROBLEM

Millions of people are offline, and it is not only about cables.

Underserved communities face three barriers at once: connectivity they cannot afford, infrastructure that is not there, and skills nobody taught them. Fix one and the other two still block the door.

High cost of connectivity

Data and devices stay out of reach for many households.

Limited infrastructure

Remote areas may have neither reliable power nor internet.

Limited digital skills

People may have no accessible way to learn and build confidence.

SECONDARY RESEARCH

Four sources, and what each one changed.

01

25.1% of rural Kenyan households have an internet connection, against 54.1% of urban households.

CA / KNBS 2023-24 Kenya Housing Survey

Build for far less connectivity than an urban user has, and for it to come and go.

02

Infrastructure, affordability and socioeconomic factors all shape whether people adopt technology.

CA / KNBS ICT analysis

Solve cost, access and usability together. Connectivity alone is not the product.

03

Gaps in basic and advanced digital skills limit how far digital tools actually get used.

World Bank

Design for low confidence: simple flows, guidance in place, plain language.

04

Mobile and offline learning models already work, including M-Shule in Kenya and an offline resource centre in the North East.

UNESCO

Learning has to keep working after the connection goes.

The opportunity was never to hand people internet. It was to turn temporary connectivity into access that lasts.

THE SOLUTION

How SolMoTech works.

01

Mobile hub

Solar-powered vans visit communities on a scheduled route.

02

Connectivity

Satellite internet reaches the van, local Wi-Fi reaches the people near it.

03

Digital platform

The app carries learning, resources, opportunities and coaches.

04

Opportunity

Skills, education, work and coaching, built on top of the visit.

WHAT I CHANGED

My first version solved the wrong half of the problem.

Three versions across two years. V1 was about getting people online. It worked, and it missed the point. The van leaves. So V2 is built around the part I had ignored: what a person still has after the connection is gone.

The challenge wasn't simply providing internet access. It was designing an experience that remains valuable when connectivity is temporary.

LINDA GITAU, SOLMOTECH CASE STUDY
WHERE IT STARTED · 14 FRAMES

Before either version, it was a greyscale wireframe called Solar Hub.

Built as a course milestone. No colour, no design system, no brand, just the flow. Everything below is what happened to it over the next two years. The original is still live, and you can click through the whole thing.

Open the original prototype
V1 ORIGINAL WIREFRAMEV2 CASE STUDY ITERATION
Home screen, before and after. The V1 login screen next to the V2 dashboard showing connection state, the next hub visit, learning progress and opportunities.
The home screen stopped being a door and became a dashboard. V1 opened on a login form, which tells a person nothing. V2 opens on the three things they actually came for: whether they are connected right now, when the van comes back, and what they were part way through learning.
V1 ORIGINAL WIREFRAMEV2 CASE STUDY ITERATION
Main screen, before and after, showing the shift toward connection state and offline availability.
Connection state became a permanent part of the interface. Connected, limited, offline. In V1 you found out you had lost the network by tapping something and watching it fail. In V2 the app tells you first, and shows you what still works.
V1 ORIGINAL WIREFRAMEV2 CASE STUDY ITERATION
Services, before and after, showing downloadable and offline-available resources.
Resources learned how to leave with you. Downloads, offline availability, and sync when the signal returns. This is the whole V2 thesis in one screen: the value has to survive the van driving away.
V1 ORIGINAL WIREFRAMEV2 CASE STUDY ITERATION
Schedule, before and after, showing the upcoming hub visit made concrete.
The schedule stopped being a list and became a promise. A place, a date, a time, and how many seats are left. If the whole service rests on a van arriving, the interface has to be specific about it.
V1 ORIGINAL WIREFRAMEV2 CASE STUDY ITERATION
Service detail, before and after, showing coaching brought alongside the learning content.
Coaching moved next to the learning, not into a separate world. Self-directed content only carries people so far. Putting a real person one tap from the lesson is what turns a resource library into support.

THE PROTOTYPE

Watch someone actually use it.

Two minutes, unedited, the V2 prototype from home screen to booking a coach.

SOLMOTECH V2 PROTOTYPE · SCREEN RECORDING · NO SOUND

THE V2 SCREENS

Eight screens from the shipped prototype.

HONEST STATUS

What I still do not know.

SolMoTech is a self-initiated concept. The research is real and cited, the hypotheses are not yet validated, and I would rather say that than imply otherwise.

01

Discoverability

Can a first-time user find when and where the next hub visit happens?

02

Offline learning

Can someone download content, disconnect, and pick up where they left off?

03

Navigation

Can people finish key tasks with nobody sitting beside them?

04

Coaching

Do people understand the value, and feel confident enough to book?

05

Service model

Would people come back, and treat it as worth relying on?

CONCEPT PROTOTYPE READY FOR USER VALIDATION

Download the full deck PDF · 16.5 MB · 34 SLIDES · OPENS IN ANY BROWSER

PROJECT 02 · WANDERLUST

A booking flow that does not lose you halfway.

Travel apps tend to be beautiful until the moment you try to pay. I designed WanderLust as one unbroken run: browse a place, pick a flight, check the summary, pay, and land on a confirmation you can actually read. A concierge sits alongside it for the questions a booking form cannot answer.

I did not research this problem. I work in it. My day job is administrative assistant at a tour company, managing client bookings, itineraries and travel documents for local and international trips. Every friction point this flow is built around is one I have hit in real work: the changed flight, the booking that will not confirm, the client who cannot find their itinerary an hour before the airport.

WanderLust splash screen with the sign up and log in choice.
01Arrive
WanderLust explore screen, browsing destinations by type.
02Explore
WanderLust flight search results with fares and times.
03Choose
WanderLust booking summary showing the trip and the total before payment.
04Check
WanderLust payment checkout screen.
05Pay
WanderLust booking confirmation with the trip details.
06Confirmed

Dark by default, and legible with it

Travel happens in airports at night. The whole system is built on a deep violet ground with one bright accent, so a boarding gate at 5am is still readable.

The concierge is the differentiator

Booking engines answer what is available. A person answers what you should do. WanderLust puts that one tap from the itinerary.

Trips, not transactions

The profile counts journeys rather than orders, so the app remembers what you did instead of what you spent.

WanderLust home screen with a greeting, travel stats and browse-by-type shortcuts. WanderLust concierge screen. WanderLust profile showing number of trips taken. WanderLust profile settings screen. WanderLust payment successful screen.

SCOPE · UI DESIGN AND CLICKABLE PROTOTYPE. THE WRITTEN CASE STUDY IS STILL IN PROGRESS, AND I WOULD RATHER SAY SO THAN PAD IT OUT.

PROJECT 03 · UZIMA WATER

A meter reading is a number. This had to be an answer.

A smart water meter produces data all day and tells a household nothing. Uzima turns that stream into the four things a person actually wants to know: how much today, is anything running right now, is the meter healthy, and what will the bill be.

Where this comes from, stated plainly. Uzima is my bachelor thesis project for my BBIT degree. Self-initiated, and still in progress. The technical half is a smart water metering system with a SQL database behind it, researched against water access in Kajiado County. What you are looking at below is the design half: the interface I built on top of that work. It is a design, not a deployed product, and I would rather tell you that than let it look like more than it is.

The Uzima Water dashboard, showing today's usage, live flow rate, meter status, monthly total, and a 24 hour usage curve.
The dashboard leads with today's usage and live flow rate, because a running tap you cannot see is the expensive problem.

Four numbers before anything else

Usage today, flow rate now, meter status, monthly total. Everything else on the page is available underneath, and nothing competes with those four.

A curve beats a table

The 24 hour usage graph makes a leak visible as a shape. You do not have to read numbers to notice that something ran all night.

Light interface, on purpose

This one runs bright while WanderLust runs dark. A utility dashboard gets read in daylight, on a laptop, by someone in a hurry.

Uzima Water process page.
Process
Uzima Water meters page listing connected meters and their status.
Meters
Uzima Water billing page.
Billing
Uzima Water search page.
Search
Uzima Water profile page.
Profile
The Uzima Water public landing page.
Landing

SCOPE · BACHELOR THESIS PROJECT, SELF-INITIATED AND STILL IN PROGRESS · SQL-BACKED ON THE TECHNICAL SIDE · THE INTERFACE SHOWN HERE IS DESIGN WORK, NOT A SHIPPED PRODUCT.

TRY IT

Press and hold.

This is the whole job in one gesture. Scattered pieces, held steady, until they become something a person can use.

INSIGHT BECOMES INTERFACE.

HOLD TO RESOLVE

CONTACT

Seen enough?

Open to opportunities, collaborations and interesting problems. Tell me what you are working on.

Get in touch