18 May 2026
Why we built a Layton successor for the web
A small team in Paris on what we missed about Professor Layton on the DS, what happened to that quiet when puzzle games moved to the phone, and the puzzle game we are trying to build for the browser instead.
The first Layton most of us touched was a DS we shared with a sibling, an afternoon long, on a couch that wasn't ours. The room had the kind of grey light that sits over Paris from October to March. The sound was off because someone was sleeping. The puzzles were fine. What we remember, twenty years later, is the pause between them.
Layton on the DS was a puzzle game with breath in it. You solved a tile-sliding piece, watched a small cutscene of a hat tipping, walked into the next room, and the room waited for you. Nobody asked you to rate the puzzle. Nobody sold you a hint. The clock didn't shrink. You could put the console face-down on the cushion, get up, make a tea, come back, and the puzzle was still there at exactly the screen you'd left. That was the contract. The world held while you stepped away from it.
We started Cora's Atlas because we wanted to make a puzzle game that kept that contract on the web. That sentence sounds smaller than the project actually is, and we know it. But the more we worked on it, the more we realised the contract was the thing — everything else was downstream.
What the DS afternoon was actually doing
A Layton chapter on the DS was structured like a short story with puzzles in the margins. You walked into a town. A character had a problem. The problem was a puzzle, but the puzzle was also the character — a baker who couldn't divide a cake, a clockmaker whose gears didn't match, a girl whose dog wouldn't choose a colour. You solved the puzzle and the town moved by one frame. Another character appeared. Another problem.
The thing we missed, when we tried to describe it later, was that the puzzles were the slow part. The fast part was the world. Layton's London or village or train was always one screen tap from where you were, and the puzzle was the doorway. You weren't being asked to solve a hundred puzzles in a row. You were being asked to walk through a place.
The DS knew it was being held in two hands by one person, in one room, with no notifications and no other tabs. That assumption is doing more work than the writing did. It let the puzzle be a thing you could stop in the middle of without anything punishing you.
We do not think this is nostalgia. We think it was a design choice the DS made by accident, because it had no other context to compete with. The puzzle game inherited the silence of the device.
What happened to the pause
When puzzle games moved to the phone, the pause was the first thing that got cut. You can see it in the way the genre re-shaped itself between roughly 2012 and 2018. The hint was no longer a coin in a satchel; it was a video ad. The level select was no longer a town; it was a grid of locked boxes. The puzzle was no longer a small detail in a literary world; it was the entire screen, and the screen was a slot.
We don't have a grievance against the phone. The phone is a perfectly good place to solve a puzzle on a train. What the phone struggles with is the part of Layton that wasn't the puzzle. The phone wants you to come back tomorrow. Layton wanted you to stay this afternoon. Those two designs are not the same animal.
Some of the casualties were visible. The literary tone went first, because tone is expensive and ads pay per impression. The hand-drawn art went next, because hand-drawn art doesn't scale to a content pipeline that needs a new world every six weeks. The slow chapter, the patient one with three rooms and four characters and one secret puzzle hidden behind a bookshelf, became uneconomic. Nobody banned it. It just stopped being the thing that paid for the next quarter.
Some of the casualties were quieter. The biggest one, for us, was that the puzzle stopped being the doorway to anything. It became the destination. You opened the app, you solved the puzzle, you closed the app. There was no town on the other side of the puzzle. The puzzle was the whole room.
What we are trying to build
Cora's Atlas is a narrative puzzle game for the browser, set across five fictional nations. There is a cartographer named Cora who is the lens, a family named Verras whose history holds the spine, and a saga that we estimate will take a thoughtful player around fifty hours across five years of writing. The puzzles are cryptograms, lateral-thinking riddles, and observation pieces — direct descendants of the Layton vocabulary, set inside a world that we drew ourselves.
We chose the browser for three reasons. First, the browser is the only platform where two people in two countries can both play the same puzzle on a Wednesday morning without either of them downloading anything. Second, the browser lets us ship a new puzzle every day without an app-store review pipeline that takes a week. Third, the browser lets us speak French and English from the same URL, which is how we work and how a large part of our audience reads.
We chose subscription, not ads. The reason is the contract from the DS afternoon. The moment you put an ad in a puzzle, the puzzle is no longer a doorway; it is a toll. We charge a small monthly fee from the players who want the full saga, and we keep a generous free tier so a curious visitor can solve enough puzzles to know whether the world is for them. We do not show ads. We do not sell coins. We do not put a thirty-second video between you and a hint. We can promise this because we picked a business model where the promise costs us nothing to keep.
We chose hand-curated, not procedural. Every puzzle in Cora's Atlas was sketched on paper first by someone who had to walk away from it twice and come back. Every character was drawn before any puzzle was written for them, so the puzzle could quietly reference a person the player already half-knew. Every nation has a calendar, a council, a family argument three generations old, and a coffee shop with a name that means two things. The world had to be there before the puzzle could be the doorway to anything.
We chose narrative arcs that take fifty hours, not five. A daily puzzle in Cora's Atlas is a small piece of a chapter. A chapter is a small piece of a nation. A nation is one fifth of the saga. The structure is recursive on purpose. We wanted a player who solves their puzzle on a Wednesday to know that the puzzle was a doorway to a room that was a doorway to a town that was a doorway to a story that took five years to write. That sentence is what we mean when we say "Layton successor."
We are not a studio. We are a small team in Paris, anonymous on purpose, with day jobs and a shared spreadsheet of puzzle drafts that goes back further than we admit. We write in English and French because we live between the two and we wanted the saga to feel native in both. We ship slowly. We answer the support emails ourselves. Most of the things you can buy in the game are cosmetic. There is no leaderboard for the saga, only for the daily puzzle, because the saga is not a race.
The world for the puzzles to be doorways into lives at /atlas. It is, at the moment of writing, one nation, eight chapters, one hundred and nine puzzles, and twenty-three characters. Four more nations are in the workshop. The map is open if you want to walk through it.
Cora's note: The DS we shared on the couch is, as best we can remember, still in a drawer in someone's parents' house in the eleventh arrondissement. The cartridge that was in it that afternoon was Curious Village. The puzzle we were stuck on was the one with the wolves and the chickens. We never solved it that day. We solved it the next morning, before school, on the same couch.
