What we believe about making mobile games
These are the convictions that shape how we work — not a mission statement written for a wall, but the actual beliefs that show up in how we give feedback, build prototypes, and talk to the people who trust us with their ideas.
← Back to homeWhere this all starts
Pocketforge grew out of a specific frustration: that indie mobile game creators — people with real ideas and genuine drive — often couldn't find a development partner that was scaled for where they actually were. Too small for large studios. Too serious for generalist freelancers.
So the foundation here is simple: build services that are genuinely useful to someone at the beginning, without requiring them to already have a team, a budget, or a complete design document. Start where they are, not where it's convenient to start.
That belief shapes everything that follows — the scope of our services, the way we give feedback, and the tone we bring to every conversation.
What we think mobile games can be
Mobile is still the most accessible game platform that has ever existed. Anyone with a phone can play. Anyone with a computer and enough patience can ship. That accessibility is something worth protecting.
We believe the best mobile games come from creators who understand the medium specifically — who design for short sessions, for thumbs rather than keyboards, for moments stolen in the middle of a day. That literacy takes time to develop, and part of what we do is help creators develop it earlier.
The goal isn't to make every project into a hit. It's to give every project a fair chance at finding out whether it has something worth building on.
What we actually believe
Honest feedback is a form of respect
Telling someone what they want to hear is easy. It's also fairly useless. We believe that giving someone the full picture — including the parts that need work — is a more respectful and genuinely caring way to engage with their project.
Early testing saves late rework
The cost of finding a problem in a concept note is a morning. The cost of finding the same problem after three months of development is enormous. We think the most valuable work often happens at the very beginning of a project.
Touch feel isn't a detail — it's everything
Mobile games are held in hands. The way a mechanic responds to a thumb tap shapes whether someone plays for three minutes or thirty. We take that physical dimension seriously in everything we build and review.
Clarity is a product in itself
Leaving a conversation or a document knowing exactly what to do next is valuable. We put effort into making our feedback and deliverables clear enough to act on immediately — not to interpret later.
Pacing should follow the project
Some ideas need time to breathe. Forcing a timeline that doesn't fit the project produces work that feels rushed. We'd rather be clear about how long something will take than hustle through a deliverable that doesn't quite land.
The stores are not the finish line
Publishing a game to an app store is the start of a much longer relationship with players, not the end of a production process. We think about launch prep with that in mind — not just what needs to be checked, but what position it sets the project up for.
How these beliefs show up in our work
Notes written to be used, not filed
When we deliver an Idea Review, we write the summary the way we'd want to receive it — specific, direct, and organised around what to do next. No fluff added to make it look like more work.
Prototypes built for feel, not presentation
Our Prototype Sprint delivers a real build that can be installed on a device. It's rough enough to be fast, complete enough to test the thing that actually matters — how the mechanic feels in your hand.
Store prep that reflects the actual project
The Tune-Up isn't a generic checklist photocopied from a forum post. Every guide and set of notes we deliver is written for the specific game being submitted — its genre, platform, and likely reviewer concerns.
Communication that doesn't make you chase
We reply to first messages within a couple of working days and keep you informed if something shifts. You shouldn't need to follow up twice to get a straight answer from us.
This is about people, not pipelines
Every project that reaches us belongs to a person who spent real time and care on something that matters to them. We don't treat that lightly. The feedback we give is considered, not templated. The builds we make are real builds, not demos assembled for a screenshot.
We try to remember that the person asking about their concept has usually been thinking about it for weeks before they sent the first email. That context shapes how we respond — with attention, not efficiency.
That doesn't mean we're soft on quality. It means we think the work is worth doing carefully, and that the person receiving it deserves to see that care in how it's delivered.
We improve deliberately, not reflexively
There's a version of "staying current" that means chasing every new tool or technique as it surfaces. That version produces a lot of noise and not much depth. We take a different approach.
When we update how we work — whether that's how we structure an Idea Review note, how we handle touch input in a prototype, or how we interpret App Store guidelines — it's because we've found a specific problem with the old way and a specific improvement in the new one. Not because something newer became available.
That deliberateness is slower in some ways. It's more reliable in others.
Openness as a working principle
Our prices are published. What each service includes is described clearly. If we think a service isn't the right fit for your project right now, we'll say so. These things aren't policies — they're just how we think professional work should operate.
We also try to be honest about what we don't do. We're not a full-stack development studio that can take a game from concept to finished product at scale. We're a focused set of services built for specific moments in the indie development process. Being clear about those edges is part of being trustworthy.
We see this as a working relationship
The way we see it, we're not service providers in the traditional sense — we're a pair of experienced eyes added to your project for a defined period. That means we bring our perspective, but we also listen. Your context matters. Your instincts about your own game matter.
If something in our feedback doesn't feel right, we expect you to push back. If a part of the prototype build goes in a direction that doesn't match what you had in mind, we want to know. Good collaboration requires that kind of back-and-forth, and we create space for it intentionally.
We keep the relationship simple: clear scope, honest output, no obligation to continue unless it makes sense for you.
Thinking past the immediate output
The notes outlast the engagement
An Idea Review you received six months ago should still be useful on the next project. We write with that in mind — not just for the immediate decision, but for the thinking it might inform later.
Prototypes as learning tools
What you discover by playing a prototype matters beyond that mechanic. The lessons about loop timing, input response, and session feel transfer to every mobile game you make after this one.
Launch prep that builds confidence
Going through a thorough store review once teaches you what to look for the next time. We try to explain our reasoning, not just our conclusions, so the knowledge stays with you.
What this philosophy means in practice for you
You'll receive feedback that is honest about weaknesses, not filtered to be more comfortable. That's a feature, not a rough edge.
Deliverables will be scoped to what your project actually needs, not padded to justify a higher price point.
If we think a different service fits your project better than the one you enquired about, we'll say so before you commit.
Communication will be direct and timely. You won't be left wondering where things stand.
The work we do together belongs to you. We have no interest in retaining rights to notes, builds, or any part of your project.
If this feels like the right kind of partner
You don't need a polished pitch to reach out. A few lines about where your game idea is right now is enough to start a useful conversation.
Start a conversation