What we believe
Good games come from people who care about them.
We think the conditions that allow a developer to make something personal and honest matter as much as the tools they use. This page explains how we see that.
← Back to homeOur foundation
Where all of this starts.
Spritely grew from a simple observation: many of the most interesting mobile games were made by one person or a very small group, often in evenings and weekends, with modest tools and a lot of patience. Those games tend to have a quality that bigger productions sometimes struggle to replicate — a sense that the person who made it genuinely wanted it to exist.
We built a studio around supporting that kind of making. Not because small means amateur, but because small, personal games deserve support that actually fits them.
Philosophy and vision
We think indie games are worth taking seriously.
Not in a grand, manifesto-y way — just in the quiet sense of giving them proper attention and care. We believe that if someone has spent their time and energy making something, the support around that thing should rise to meet the effort.
What we're working toward
A world where more indie developers finish their first game — not because it was made easy, but because they had the right support at the right moments, without having to spend beyond their means or lose their voice in the process.
How we think about transformation
For us, transformation isn't about producing a polished commercial game. It's about a developer coming out of an experience more capable, more confident, and with a project that genuinely reflects them — however modest in scope.
Core beliefs
A few things we hold to be genuinely true.
Pace is a design decision
How fast you work shapes what you make. Forcing a pace that doesn't fit produces work that shows the strain. We believe giving developers room to move slowly when they need to is part of what makes the end result worth playing.
Honesty is more useful than encouragement
We'd rather tell a developer that something isn't working — kindly, with suggestions — than applaud everything and watch them build toward a wall. Good feedback, offered with care, is one of the most useful things we can provide.
The creator's voice should survive the process
Too many games lose their distinctiveness during development — sanded down by convention, tools, or well-meaning advice that prioritised the standard over the personal. We try not to do that.
Mobile is a real creative medium
Phone games are often dismissed by people who haven't thought carefully about them. We think the constraints and the reach of mobile make it a genuinely interesting place to make games — not a consolation prize.
Small scope is not a limitation
A short, coherent game that does one thing well is more interesting than an ambitious game that does ten things poorly. We believe in helping developers find and respect the right size for their project.
Support should build independence
We're not interested in a developer needing us indefinitely. The goal is for them to emerge from working together more capable of doing the next thing on their own.
How beliefs become behaviour
What these ideas look like in practice.
We don't set your schedule
When a project needs to pause because life got complicated, that's fine. We pick back up when you're ready. We track where things are so nothing gets lost.
We explain our thinking
When we suggest something, we say why. When we think something won't work, we say that too — not to be difficult, but because understanding the reasoning is more valuable than just following instructions.
We ask before we change things
Your game has a particular feeling and direction. Before suggesting something that would alter that, we check in. Your instincts about your own work matter.
We stay in scope
Feature creep is one of the most common ways indie projects stall. We gently help you hold the line on what the project is, so it can actually get finished.
The human part
Every project is made by a person in a specific situation.
We don't think of the people we work with as clients in the abstract. Noemí is building a puzzle game in the gaps between work shifts. Riku has been working on a small narrative game for two years and isn't sure what to do next. Saoirse has a playable build and no idea how to present it to the world.
These situations are different and deserve different things. We don't apply a fixed process to everyone — we find out where a person actually is and offer something useful to them specifically.
This takes a bit more time than a template approach. We think it's worth it.
How we keep getting better
We improve slowly and on purpose.
We're not interested in constant reinvention for its own sake. When we change how we do something, it's because we've noticed a real problem and found a thoughtful solution — not because a trend suggested we should.
Learning from each project
Each developer we work with teaches us something. What kinds of questions come up repeatedly. Where the friction tends to appear. We fold that back in quietly.
Keeping what works
Some of our approaches haven't changed much in years because they're genuinely useful. We don't replace working methods just because something newer exists.
Integrity
We say what we mean and mean what we say.
Our prices are what they are — no add-ons discovered halfway through. If something isn't going well, we say so. If we don't know something, we say that too rather than bluffing. We think transparency builds something more durable than the impression of certainty.
We also try to be accountable for our advice. If we recommend something that doesn't work out, we don't quietly move on — we think about what went wrong and share that with the developer honestly.
Working together
We think of this as a collaboration, not a transaction.
When it's working well, working with us feels like having a knowledgeable, calm friend in the room — someone with relevant experience who is genuinely on your side and wants the game to come out well.
Shared ownership
We care about the outcome, not just our contribution to it.
Mutual respect
You know things about your game we don't. That knowledge matters.
Genuine interest
We're not going through the motions. We find your project interesting.
The longer view
We think about what happens after the project ends.
A finished game is one thing. A developer who comes out of the experience with a clearer sense of how to make the next one is something more durable. We try to be useful in a way that compounds — leaving each person in a slightly stronger position than before we worked together.
That means explaining our reasoning, pointing toward resources, and occasionally saying "you don't need us for this part — here's how to do it yourself." We'd rather be remembered as genuinely helpful than as people who made themselves seem indispensable.
What this means for you
What you can expect from us, in plain terms.
If you work with us, these are the things we commit to — not as policies, but as a genuine expression of how we want to show up.
We'll be honest with you, even when the honest thing is slightly uncomfortable to say.
We'll respect your pace and not push you faster than feels right.
We'll keep your vision at the centre — we're here to support it, not replace it.
We'll be transparent about costs, scope, and anything that changes.
We'll explain what we're doing and why — you shouldn't have to trust us blindly.
We'll leave you better equipped for your next project than you were at the start of this one.
Work with us
If this way of working sounds right, we'd like to hear from you.
Tell us where you are and what you're trying to make. We'll take it from there, honestly and without pressure.
Get in touch