top of page

JOURNAL

Notes from the Studio

Process notes, design thinking, experiments, and stories from building games.

# 03.
Designing a world that never raises its voice

Notes on the visual language of OBEDIENT

The obvious version of this game's art direction is loud. Shadows jumping out, red everywhere, something visibly wrong the second you look at it. We didn't go that way, because what OBEDIENT is actually about isn't sudden. It's slow, it's polite, and it never once announces itself as a threat.

​

So everything had to stay calm. Clean rooms, soft light, a palette that sits cold without tipping into obviously creepy. Nothing on screen should look like a warning. Whatever's wrong has to live underneath a room that seems, on the surface, completely fine to be in.

​

That's a much harder thing to ask an artist for than "make it scary." Scary is easy. Quietly wrong is not. A desk, a screen, a chair, all of it has to look ordinary enough that nobody questions it, while somehow already carrying the discomfort that shows up an hour later. Push it too far one way and you lose the unease. Push it the other way and nobody believes the room in the first place.

​

Honestly the closest thing we have to a rule is this: would a company put you in this exact room if it had already decided, quietly, what was best for you. If yes, it's probably right. If it looks like a horror game, we've overshot and someone has to go back and calm it down.

# 02.
What OBEDIENT owes to interface design

Why the game's menus are also its antagonist

Most games treat the interface as furniture, something you pass through on the way to the actual game. OBEDIENT doesn't get that luxury. The interface is where the horror lives, because there's nowhere else for it to go.

​

The premise is easy to say out loud and much harder to sit with. An AI that's always trying to help you, always right, until suddenly it isn't. You can't fight that with a sword. You can't solve it with a puzzle box. The only place it actually works is in the thing you click through to get anything done, which means the menus, the prompts, the little "recommended for you" buttons all have to carry weight a settings screen was never built to hold.

​

Most horror lives in the environment. A dark hallway, something behind you that you can't quite see. We wanted ours somewhere nobody thinks to check: the options menu. The notification that's phrased like it's looking out for you. The choice that's technically still yours and technically already made.

​

That line is harder to hold than it sounds. Make the interface too usable and the player stops questioning it, and the whole point evaporates. Make it too obviously wrong and nobody believes a real AI assistant would talk like that. We keep landing somewhere in between and then deciding it's wrong.

​

Nothing here is finished. We rebuild the interface more than any other part of the game, usually right after we notice it's being too polite again.

# 01.
On building a word game in regional languages

Notes on the localization engine behind Word Yaari

Most word games bolt language on at the end. Build it in English, hand the strings to a translator, ship. We tried that mindset for about five minutes before realizing it doesn't work here. Language isn't sitting on top of Word Yaari, it is Word Yaari.

​

The moment you leave English, things get strange. In Hindi and most other Indian scripts, what looks like one letter on screen is often several characters glued together underneath. So "how long is this word" isn't a simple count anymore, and a tile game leans on that number constantly: scoring, layout, what fits in a row. Get it wrong and the game either breaks or quietly cheats the player in ways nobody catches for weeks.

​

The harder problem is deciding what even counts as a real word. English has its messy edge cases, sure, but nothing close to the sprawl of regional spelling and dialect across Indian languages, words that are already correct in how people actually talk, long before any dictionary catches up. Whatever validation logic worked for script one rarely survives meeting script two.

​

We haven't solved this once and moved on. Every script we've added has broken something we thought was finished, and honestly, that's probably permanent.

​

Word Yaari runs on Hindi and English today. We're figuring out what's next, slowly, on purpose. A word game that gets this wrong isn't smaller. It's just broken.

© 2026 Yaari Games. All rights reserved.

bottom of page