Product design · Mobile · Early career

I design mobile products that stay clear when things get busy.

I studied Industrial Design Engineering at TU Delft and I’m moving into product design full-time. I care about simple flows, honest choices, and shipping work with real people — not just pretty screens.

Selected work

Two real products. I start from the problem, then show the decisions and screens.

Case 01

Speelopvliegers

Problem: Design a group party game for Dutch women 50+ that still feels easy when everyone is chatting, someone is holding the snacks, and nobody wants a complicated setup. Joining should be obvious. The free trial should feel fair. Paying once should feel clear.

Role: product design and delivery with client Suus · host mobile app + web join · 2025–2026

What I worked on

Main game path, 50+ usability rules, join model, free-to-unlock story, restore/legal screens, and fast feedback loops with the client.

Constraints

Mixed tech confidence in a group, two surfaces (app + web), one-time purchase only, and client approval on content and tone.

Speelopvliegers screen 1
Entry / product surface
Speelopvliegers screen 2
Core play state
Speelopvliegers screen 3
Group interaction
Speelopvliegers screen 4
Results / reveal moment
Speelopvliegers screen 5
Progress / session continuity
Speelopvliegers screen 6
Unlock / commercial moment
One host app, web join for the rest

Only one person needs to download. Everyone else scans a QR and plays in the browser. That keeps the group moving.

Designed for 50+

Bigger type, bigger taps, plain Dutch, one main action per screen. Not “accessibility later” — this is the product bar.

Honest free trial → unlock

Five free questions first. Then a clear one-time purchase. No subscription wording that confuses people.

Where it landed: A full multi-device game loop ready for release testing, with paywall, restore, legal and join flows shaped by real client feedback. More screens and process visuals will land here as I add portfolio assets.

Case 02

Stira

Problem: Design period tracking where sensitive cycle data stays privacy-first, and optional partner sharing only happens with consent people actually understand.

Role: product design and build · mobile · ongoing · usestira.com

Point of view

In this category, trust is the product. Good privacy UX is mostly clear timing, clear copy, and real control — not only security claims.

What’s here now

The problem and design principles. UI walkthrough comes next when I add more app screens.

Privacy-first by default

Keep the most sensitive data under the user’s control first, even if that makes sync and sharing harder later.

Sharing only with consent

Partner features should never “just work” by leaking data. Consent has to be explicit and reversible.

Calm over clever

Less anxiety, fewer dark patterns, clearer states. Long-term trust beats short-term growth tricks.

Stira wordmark

About

Why design, and why now.

I’m changing lanes on purpose

Right now I work as an AI Engineer. I ship useful things, mostly on Power Platform. I’m good at delivery. I’ve also learned what drains me: taking tickets in, sending work out, and barely touching the actual problem.

I want to grow as a product designer. Define the problem. Shape the journey. Care about how the product feels in someone’s hand. That’s the work I want to spend my days on.

I’m early in my design career and honest about that. What I already bring is shipped product judgment, real stakeholder work, and enough technical literacy to move quickly with engineers.

What I’m building skill in

Problem framing User flows Mobile UX Stakeholder collaboration Accessibility-minded UI Figma (learning fast) Prototype via real builds

Education & work

BSc Industrial Design Engineering — TU Delft, graduated July 2025

AI Engineer — Global Software Solutions, Teteringen, since Sep 2025

Say hi

Open to early-career Product Designer roles in mobile.