Questions About Game Development?
We get asked plenty. Everything from platform choices to project timelines to what actually happens when you work with us. Here's what clients typically want to know before we start building together.
Real Questions from Real Clients
Over the years, we've noticed patterns in what people ask before starting their game projects. And honestly? They're good questions. The kind that show someone's done their homework.
Some want to understand technical limitations. Others are curious about our process or how we handle unexpected challenges mid-project. A few just want to know if their idea is actually feasible.
We've gathered the most common ones here. If your question isn't covered, that's what conversations are for.

Common Questions
Sorted by topic because nobody likes scrolling forever
Project Scope & Planning
How long does a typical mobile game project take?
It varies quite a bit. A simple puzzle game might take 3-4 months from concept to launch. Something with multiplayer features, custom artwork, and deeper mechanics? You're looking at 6-9 months minimum. We've had projects run longer when clients want to iterate based on beta feedback, which honestly tends to produce better results.
Do you work with clients who already have a development team?
Absolutely. Sometimes teams need specific expertise for particular platforms or want an external perspective on performance optimization. We've collaborated with in-house developers on plenty of projects. Clear communication channels make it work smoothly.
What if my game idea changes halfway through development?
Happens more often than you'd think. Good ideas evolve when you actually see them in action. We build flexibility into project structures, but significant changes do affect timelines and budgets. The key is having honest conversations early about what's a refinement and what's a pivot.
Technical Questions
Which platforms do you develop for?
Primarily iOS and Android, which covers most of the market. We can build native apps or use cross-platform frameworks depending on project needs. The choice affects performance, development time, and how easily you can update things later.
Can you integrate existing backend systems or APIs?
Yes. If you've already got user authentication, leaderboards, or payment systems you want to keep using, we can connect to them. Sometimes existing systems need modifications to work efficiently with mobile platforms, but that's part of the planning phase.
What about multiplayer functionality?
Real-time multiplayer adds complexity. It requires robust server infrastructure, careful network optimization, and thorough testing across different connection types. We've built turn-based and real-time multiplayer games, but it significantly impacts both development time and ongoing maintenance needs.
How do you handle game performance on older devices?
Testing across device ranges and optimizing where needed. We identify your target audience and their typical devices during planning. Sometimes that means scaling back visual effects on older hardware or creating different asset quality tiers. Performance isn't glamorous work, but it matters for player retention.
Working Together
How involved do I need to be during development?
Depends on your preference and the project. Some clients want weekly check-ins and hands-on involvement with every decision. Others prefer milestone reviews where they test builds and provide feedback. Both approaches work, but more communication usually means fewer surprises.
What happens after the game launches?
Launch is really just the start. Games need updates for new OS versions, bug fixes if issues emerge, and often content updates to maintain player interest. We offer ongoing support arrangements, or we can document everything thoroughly if you want to handle it internally.
Do you sign NDAs?
Of course. Many clients have competitive concerns or unique mechanics they want to protect. We're happy to review and sign reasonable confidentiality agreements before discussing project details.
Getting Started
What information do you need for an initial consultation?
A clear description of what you want to build helps. Target platforms, any specific features or mechanics you're envisioning, your timeline expectations, and whether you have existing assets like artwork or music. The more context we have, the more useful that first conversation becomes.
Can we start with a prototype before committing to full development?
Definitely. Prototypes are brilliant for testing core mechanics and seeing if the game feels right before investing in full production. They're also useful for pitching to stakeholders or potential publishers if that's your path.
What if we're based outside the United Kingdom?
Not an issue. We've worked with clients across different time zones. Video calls, project management tools, and clear documentation keep things moving. Time differences sometimes mean responses aren't instant, but we've made it work smoothly with clients from various regions.

"They answered every question without making me feel like I was asking too much. The transparency about what was realistic versus what would require compromise was refreshing. No overselling, just honest assessments."

Liselotte Vanhanen
Independent Developer

"I had concerns about technical feasibility for some features I wanted. Rather than just saying yes to everything, they explained trade-offs and suggested alternatives. That honesty early on saved us from problems later in development."

Cressida Tollefsen
Studio Producer
Project Timeline Reality
Development Insight
Most mobile game projects take longer than initial estimates suggest. Not because of poor planning, but because good ideas emerge during development that are worth exploring. Build buffer time into your expectations. Rush jobs rarely produce games people actually want to play more than once.
Still Have Questions?
If your specific situation didn't get covered here, let's just talk. Sometimes the best way to answer questions is through a proper conversation where we can understand your project context.
We're not trying to sell you on anything during initial discussions. Just figuring out if what you need matches what we do well.
Get in Touch