The name is the mandate: why we called it Simple Yet Efficient
Naming a studio is mostly vanity. We tried to do the opposite — pick a name that we would be embarrassed to violate. Here is what that looks like in practice.
The name as a trap we set for ourselves
Most studio names are a vibe. Blackforge, Novacortex, Pixel Lantern. They evoke something and then get out of the way. You could swap the logo with any of ten other studios and the name wouldn't tell you a thing about the software inside.
We went the other direction. Simple Yet Efficient is not a vibe — it is a constraint. Every time we ship something, the name is a question we have to answer out loud. Is this simple? Is it efficient? If either answer is "well, sort of", we go back to the whiteboard.
It's the most annoying name in our industry, and that's on purpose.
What simple means to us
Simple is not "small." A simple tool can be thousands of lines of code, as long as the code is legible. Scene Compass is simple because the entire mental model — two hotkeys, two modes — fits on the back of a napkin. REST Express is simple because the generated code looks like code you would have written by hand on a good day.
What simple rules out:
- Plugins that own your architecture. If installing us requires three interfaces, a dependency injection container, and a ScriptableObject registry, we've already failed.
- Configuration surfaces that dwarf the feature. When the settings page is bigger than the functionality, the feature is the settings page.
- Clever internals that leak into the API. Your users should never need to know what we do with reflection or source generators. That's our problem.
What efficient means to us
Efficient is not "fast" in the benchmark-chasing sense. It means well-used — of your build time, your memory budget, your developer time. A plugin that allocates 200 KB of garbage per frame to save you 40 minutes of editor setup is not efficient. It is a trade you should be allowed to reject.
The two values fight each other constantly. The most efficient thing is often a gnarly hand-tuned mess. The simplest thing is often wasteful. The yet in the middle is where the craft lives.
Why we say it out loud
Naming ourselves after the constraint means we can't quietly drop it when a deadline looms. If we shipped a bloated, mediocre plugin under this name, the name itself would be a lie on the Asset Store page. It'd show up in every email signature, every invoice, every PR notification.
Embarrassment is a useful design tool. We recommend it.
