Case study 01iOS party game

Wetin Be Dis

A Naija party game where the culture is the mechanic.

Join the TestFlight beta
Role
Concept, design, writing, SwiftUI build
Timeline
TestFlight beta
Stack
Swift · SwiftUI · Original card system

Act 01 — The problem

A party game about forbidden words, fast guessing, and the special chaos of explaining something everyone in the room already knows.

Party games like Taboo and Heads Up work because of shared context — the laughter comes from everyone knowing exactly what you're failing to say. But their decks are culturally generic. For Nigerian players, the words, slang, food, music, and inside jokes that would actually set a room on fire simply aren't in the box.

Wetin Be Dis starts from the opposite end: what if the cultural specificity wasn't flavor on top of the game, but the game itself? Every card assumes the room shares a world — and the gameplay is what happens when you have to explain that world with your hands tied.

Act 02 — The system

The shape of the thing, before the screens.

The loop

01Prompt card“Wetin be dis?”
02Forbidden wordsEvery obvious route, blocked
03The room guessesLoud, wrong, then right
04Laughter, score, next cardThe loop is the product

Every design decision serves this loop: shorten the path to it, never interrupt it, make it louder each cycle.

Act 03 — The calls I made

Decisions, with the reasoning attached.

01

Language is the mechanic, not the theme.

The prompts are written in the voice of the room — Pidgin first, formal English never. 'Wetin be dis? Explain am well.' isn't decoration; it sets the register the whole game is played in. If the game doesn't sound like the people playing it, the chaos doesn't land.

02

Forbidden words are tuned for failure.

Each card bans exactly the words anyone would reach for first. The design goal is a specific moment: the player opens their mouth, realizes every obvious route is blocked, and has to invent a worse, funnier one. The banned list is the comedy engine.

03

Zero setup, one phone.

No accounts, no lobby, no downloads for guests. Pick categories, set the timer, pass the phone. A party game competes with the party itself — every screen between 'open app' and 'first laugh' is a screen where someone starts a different conversation.

04

Readable mid-argument, from across the room.

The gameplay card uses oversized type and hard contrast because the real play environment is loud, dim, and full of people leaning over shoulders shouting guesses. The interface is designed for the room, not the hand.

Act 04 — The screens

Real screens, not mockups of intentions.

Act 05 — Reflection

The notes I'm keeping.

01

Writing the cards is harder than building the app. The SwiftUI work was straightforward; finding prompts that are guessable, bannable, and funny at the same time is a real editorial discipline.

02

Group testing changes everything. Words I thought were obvious died in the room, and throwaway cards became the ones people quoted afterwards. The deck now gets edited the way stand-up gets edited: in front of people.

03

Cultural products earn trust through specificity. Every time the game names something precisely — a dish, a lyric, a saying — the room gets louder. Generalizing to 'reach more people' would quietly kill the thing that works.

Where it stands: Available as a TestFlight beta. Currently expanding the category packs, tuning round pacing from group play sessions, and designing the sound layer before an App Store push.

Next case study

Irie SessionsA music platform that should feel like the sessions it archives.