inkOrange Studios
TechBy Chris West••7 min read

A Studio, Finally: Why I Stopped Calling These Side Projects

inkOrange Studios is live, Exoplanet Explorer is published on Google Play, and Space Cowboy is in alpha. On what actually changes when a side project becomes something strangers install, and why I decided to take the games seriously.

Somewhere in the last few months, a stranger installed one of my apps from the Google Play store, had a problem with it, and emailed support about it. There is a support address now. Somebody answers it. That somebody is me.

That is roughly the moment a side project stops being a side project.

inkOrange Studios (opens in a new tab) is live, the first app is published, and a second one is in beta. The name is not new. I have been putting inkOrange on things for years, as a brand mark on a portfolio and a handle on a GitHub org. What changed is that it now publishes software other people install, which turns out to be a very different thing from a logo.

The honest reason

I could tell you the studio was a practical necessity, and there would be some truth in it. You cannot list an app on Google Play as a vibe. You need an entity, a privacy policy, terms, a support channel, a listing that complies with rules about what an app may advertise inside itself.

But that is the paperwork, not the reason.

The real reason is that I want to build games, seriously, as a thing I do rather than a thing I squeeze between client work and a day job. I have spent twenty years building interfaces for other people's products, and I am good at it. The projects I actually think about in the shower are the ones with physics in them. At some point you either admit that or you keep calling it a hobby for another decade.

Calling it a studio is mostly a promise to myself about how I intend to spend my time.

What the studio actually publishes

Three titles, at three different stages.

TerraForge

TerraForge

TerraForge (opens in a new tab) is the sandbox, and the oldest of them. You build a planet out of elements, give it a star and an orbit and some moons, and the simulation tells you what you made and whether anything could live there. It runs in a browser, it has a community of people building worlds in it, and it is the engine everything else grew out of.

Exoplanet Explorer screens

Exoplanet Explorer screens

Exoplanet Explorer (opens in a new tab) is the first published native app, free on Google Play. It takes every confirmed exoplanet astronomers have measured and rebuilds each one as a 3D world you can drop onto and walk around. It shares TerraForge's engine, which is the entire reason one person could ship it. I wrote about how it was built (opens in a new tab) separately, so I will not re-run that here.

Space Cowboy

Space Cowboy

Space Cowboy (opens in a new tab) is in development, and it is the one that makes this feel like a studio rather than a portfolio. It is a gravity puzzle: you slingshot around planets and stars, spending momentum instead of fuel. No simulation of planetary chemistry, no NASA catalog, no educational mission. Just a mechanic that is satisfying to get right. I wrote about taking it from a web app toward the store (opens in a new tab) a few weeks ago. It is in Android beta now, and Google requires twelve testers opted in for fourteen consecutive days before a game can launch, which is a rule I have come to appreciate for how firmly it separates the people who finish things from the people who announce them.

Alongside the games there are the educational tools, Molecular and Delta V among them, which are free, browser-based and not going anywhere. They are the part of this I would keep doing even if nobody ever installed anything.

What actually changes when you ship to a store

More than I expected, and most of it is invisible.

Version numbers stop being decorative. TerraForge and Exoplanet Explorer share one codebase but are two separate apps with two separate version numbers, and the build pipeline derives a Play version code from elapsed time rather than commit count, because squash merges can make a commit count go down and Play will reject a build whose number dropped. That is the kind of thing you learn once, painfully, and then write into a file so you never learn it again.

Two apps out of one repository also means a whole category of mistakes that did not exist before. A route file named slightly wrong and the Explorer's pages collide with the website's. An environment flag set in the wrong place and a page silently renders signed-out for every visitor with no error to tell you why. None of this is hard. All of it is sharp, and the only defense is writing the rule down the first time it bites you.

And then there is the part nobody warns you about: once an app is listed, it is listed. You cannot quietly revert. A version number burned is burned. There is a permanence to store distribution that a website simply does not have, and it changes how carefully you press the button.

Games that make you think

The studio has a line on its homepage, which is that it makes games that make you think. I want to be careful with that, because it would be easy to read as "educational games," and educational games are mostly neither.

What I mean is narrower. I like games where the fun is figuring out how the system works. Not reading a tutorial that explains it, not being told the answer, but poking at something until the rules reveal themselves. TerraForge does not explain why your planet came out as a lava world. It shows you the number and lets you work backward. Space Cowboy does not teach orbital mechanics. It just has orbital mechanics in it, and you get better by developing an intuition for them.

The principles the site lists are the ones I actually use when deciding things: fun in the first minute, learn by experimenting, and run anywhere. The third one is doing more work than it sounds like. Building for the browser first and packaging native second means a kid with a Chromebook and a parent with a phone get the same thing, and that constraint has shaped nearly every technical decision in the stack.

The unglamorous middle

I am aware that announcing a studio is the easy part. The site is up, the logo is nice, the first app has real installs. None of that is the hard bit.

The hard bit is the next eighteen months of shipping when the novelty has worn off. It is answering the support email on a Tuesday when the bug is boring. It is Space Cowboy being genuinely fun rather than merely finished. It is resisting the urge to start a fourth thing because the fourth thing is always more exciting than debugging the third.

What I have going for me is that the work itself still holds up. I have been building these things for free, at night, for years, with no studio and no store listing and no particular audience. The structure is new. The wanting to do it is not.

If you want to follow along, the studio site has a newsletter that goes out a few times a year, and Space Cowboy needs beta testers. Both are at inkorangestudios.com (opens in a new tab). And if you install something and it breaks, there is an address now, and somebody does answer it.

Comments

Loading comments...

Leave a Comment

0/2000 characters (minimum 10)