Skip to content

About the Developer

Ninte86hl edited this page Nov 20, 2026 · 1 revision

🇩🇪 Deutsch

Some people learn to program and then look for a project. For me it was exactly the other way round.

The devices came first.

The handhelds, the emulators, the menus, the many small moments when I thought: "This really ought to be easier."

That is exactly how my projects came about. Not from a wish to become a developer, but from a wish to improve things I use every day myself.

Owning a range of handhelds, I soon noticed that many devices are technically impressive but sometimes feel unfinished in everyday use.

  • A dual-screen handheld uses only one screen.
  • An Android handheld suddenly asks for the touchscreen while you are holding a controller.
  • A dock mode works technically, but not always as comfortably as you would expect from a console.

Out of these observations, ideas grew bit by bit. Ideas became concepts. And concepts finally became projects like RetroDualStation and Hugminn.

RetroDualStation started with a simple question: Why should a handheld with two screens pretend it only has one?

Hugminn came from a similar thought: Why do I have to reach for the touchscreen when I'm already using a controller?

The longer I worked on them, the clearer it became that both projects follow the same philosophy: Hardware should be allowed to play to its strengths.

Ideas, tests and AI

There was one problem, though: I'm not a professional software developer. Many ideas were bigger than my own programming skills.

That's why I use AI. Not as a replacement for my own ideas, but as an assistant, teacher, sparring partner – and now and then as a source of chaos.

Anyone who thinks projects like these come from three prompts and a free afternoon would probably have a good laugh at the reality.

At some point this led to a situation where several AIs and one developer were hunting the same bug. In the end, the solution lay in a detail nobody had on their radar.

Ever since, that story has reminded me of an important lesson: It's not the best answer that wins. It's the right question.

From that thought, there later even came a few humorous screenplays about two ravens, a director and a handful of AIs. They describe something that really happens during development: technology is only part of a project. Curiosity, creativity, patience and sometimes the ability to laugh about an absurd bug matter at least as much.

If there is one thing I've learned through RetroDualStation, Hugminn and many other ideas, it's this:

You don't have to know everything to create something. Above all, you need an idea that won't let you go. The idea comes from the person. The tools help bring it to life.

And somewhere in between, two ravens fly around and make sure it never gets boring.

Why I develop

Because good hardware deserves good software. Because small improvements make everyday life more pleasant. And because the best projects often start with a single thought:

"Surely this could be better."

Clone this wiki locally