Başar BallıözProduct Engineer
← All posts

Why I built Tibblo

Many games for children are built to keep them tapping and their parents paying. I wanted to make one I would be glad to hand over.

By Başar Ballıöz · · 3 min read

How it started

Like a lot of people my age, I had a little digital pet as a child. It lived on a tiny keychain screen, it beeped when it was hungry, and I took it far too seriously. Looking after something small, every day, was the whole game, and it was enough.

Years later I watched children around me playing pet games on phones, and the feeling was different. The pets were cute, but the games kept interrupting: an ad after a few taps, a timer asking for one more go, a shop button never far from a small finger. The adults spent as much time checking settings as the children spent playing.

I did not want to write an article about it. I build things, so I decided to build the version I would be comfortable handing over.

The rules I set before writing any code

  • No account and no chat. Nothing to sign up for, nobody to talk to.
  • Plays offline. On a plane, in the car, anywhere.
  • No analytics. The game does not track what a child does in it.
  • A grown-up check before every purchase. Coin packs exist, but a child cannot buy one alone.
  • Ads that wait. They come at natural pauses, are never personalized for children under 13, and a one-time purchase removes the full-screen ones.
  • Fair consequences. A neglected pet gets tired or sad, and every bad state has a free way back.

Those rules made a lot of decisions for me. Whenever a feature fought one of them, the feature lost. The parents' guide and the privacy policy describe exactly how each one works.

What Tibblo is

You adopt a pet and look after it by touching it, not by tapping menus: drag food to its mouth, scrub it with soap, switch off the lamp at bedtime. There is a home and a garden to decorate, a little town to explore with neighbours to befriend, and gentle mini-games that earn coins. Fenn, an orange cat, is the face of the game.

How I built it, alone

A game is a long way from the React and Next.js I write every day. A few choices made it possible:

  • Godot as the engine: open source, light, and good at 2D on phones.
  • Art drawn from code. Every pet, room and piece of furniture is assembled from scripted parts, so I can change a colour or a shape everywhere at once.
  • Sound and music made in code, so every sound in the game is original and the download stays small.
  • Automated tests for layout, the coin economy and saves. With one developer there is no QA team, so the tests are the QA team.
  • English and Turkish, with accessibility settings throughout.

Getting a children's game into the stores is its own project: Google Play's Families requirements, child-directed ad settings, a parent gate, cloud saves, and privacy pages a parent can actually read.

What I learned

Calm is harder than loud. Every engagement trick is a shortcut. Saying no to them means the game has to be enjoyable on its own, which is a much higher bar.

Design for small hands and early readers. Big touch targets, few words, icons that make sense before a child can read the label. Every screen also has to fit any phone, from small to tall, without a button slipping off the edge.

The web did not prepare me for games. There is no page that scrolls to save you. Everything has a position, a size and a state, and a save file from an older version still has to load years later. Writing tests for that early was one of the best decisions in the project.

Tibblo is getting ready for the App Store and Google Play. If you are a parent and want to know what the game does and does not do, the parents' guide is the place to start.

More posts

Godot on iOS: from an uneven 60 fps to 120 Hz with MetalA Godot 4 game stuck near 60 fps on an iPhone 14 Pro with a main thread busy only 4 ms a frame. How a phone bench and Instruments found the cause, and how switching iOS to Metal gave 119 fps. Quest pacing: measuring where a 150-level game goes flatHow I measured the story pacing of Tibblo's 763-day road from level 1 to 150, found where it went flat after level 40, and fixed it with three-step arcs, a daily limit and a 'Last time…' card.