The Direct Line to Our Studio

We design and build games for screens that fit in a pocket. If you have a concept that needs to run flawlessly on a mid-range Android device or a polished iOS title that stands out in a crowded market, our team in Istanbul is listening.

Preferred contact is email for project inquiries. We respond within one business day.

Start the Conversation
M
Mon-Fri
09:00 - 18:00
L
Location
Istanbul, Turkey (Remote)
P
Response
< 24 Hours

What We Need to Start

Streamline the discovery phase. Providing these details upfront allows us to assess feasibility and give you a meaningful response faster.

Method Note

We evaluate project scope against our current studio capacity and technical specialization (Unity, Godot). A clear brief helps us flag potential compatibility issues early.

1

Concept Clarity

A core game loop description, one-sentence pitch, or a deck outlining the player fantasy. Visual references are not required here.

2

Target Platform

Primary device type (iOS, Android, both) and minimum OS version. This dictates performance budgets and store requirements.

3

Visual Direction

2-3 reference images for art style, UI mood, or genre. This anchors our aesthetic and tech-art pipeline discussions.

4

Timeline & Budget

Rough estimates help us align on feasibility. We work with fixed-scope contracts and flexible retainers.

The Trade-off Frame

Mobile game development is a series of calculated compromises. Understanding our priorities helps you decide if we're the right technical partner.

Visual Fidelity vs. Battery Life
We prioritize 60 FPS stability on mid-tier devices. Intensive shaders may be simplified to preserve 3+ hours of continuous gameplay.
Feature Richness vs. Development Time
For indie budgets, we often recommend a single polished core loop over multiple shallow features. Depth > Breadth.
Custom Engine vs. Off-the-Shelf
We default to Unity/Godot. A custom engine is only considered if a unique mechanic fundamentally conflicts with existing tools.
Artistic Style vs. Asset Budget
If budget is fixed, we advocate for a stylized look that reuses assets smartly, rather than photorealism that exhausts resources.
Assumptions & Boundaries
  • Target: 60 FPS on Snapdragon 730G or equivalent.
  • Art Budget: Fixed. Asset reuse is a design constraint.
  • Platform: Android-first, iOS secondary. No web initially.
  • Team: You provide a dedicated point of contact for feedback.
What Changes the Recommendation

We may suggest a different engine (like Godot) if:

  • The core mechanic is 2D-heavy and needs minimal physics.
  • You have an in-house preference for open-source tools.
  • The project requires low-level memory management unusual for Unity.
Engagement Flow
1
Intro
2
Audit
3
Proposal

The Collaboration Framework

Our workflow is built for remote clarity. It’s designed to keep projects on track while giving creative space to breathe.

Methodology Note

Robustness is evaluated via weekly milestone reviews. We don't hide risk; we surface it early. The 30-day post-launch support acts as a final QA buffer against real-world device fragmentation.

Phase 1

Discovery & Pre-Prod

We define the technical scope, prototype the core loop, and lock the art style. Weekly syncs establish rhythm.

Input: Concept Doc + Refs → Output: Technical GDD
Phase 2

Production & Polish

Content implementation, integration, and iterative polish. Async updates via shared channel; consolidated feedback weekly.

Asset Handoff: Private cloud repo (FBX, PSD, code)
Phase 3

Launch & Support

We handle store submission (assets, descriptions, builds). Includes 30-day bug-fix window for post-launch issues.

Deliverable: Build + Docs + Store Assets

Common Questions?

Tap below to review.

Send a Direct Inquiry

Prefer to discuss via email? Use the address below. We handle all project briefs and initial discussions this way to ensure proper documentation.

Address
Istiklal Caddesi No: 123
Beyoğlu, Istanbul, Turkey
Hours
Mon-Fri: 09:00 - 18:00
Ready to prototype? Return to Studio Overview