Founded in Warsaw
Core team of 3 engineers from Warsaw's tech scene. First prototype built on a custom engine (now deprecated).
Constraints: 2-person team
Studio Dossier: Datreno
Polish Craftsmanship, Engineered for Play.
We build mobile games that feel as solid as they look. From the first prototype to the final polish, our work is rooted in technical precision and a player-first ethos.
Stack Compatibility Preview
v2.4.1
✔
Unity 2021 LTS
✔
Unreal 5.1
⚠
Godot 4.x (Beta)
✖
Legacy Custom Engines
Notes: Unity integration requires manual manifest edits for Android 13. Unreal requires specific plugin versions for mobile optimization.
"Visuals rendered in-engine showcasing real-time capabilities."
Flagship Title: Chrono Forge
Genre-Defining Craft
Genre
Time-Bending Puzzle RPG
Aesthetic
Dieselpunk Meets Celestial Art Deco
Player Moment: Rewinding a failed platforming sequence to discover a hidden path.
Chrono Forge
Master time manipulation to solve intricate puzzles in a world of brass and starlight.
FEATURED
Google Play Best of 2023 - Indie
Field Scenario: The 30-Second Hook
The Problem: A new player downloads Chrono Forge. They need to feel the core mechanic immediately, but the first puzzle is complex. How do we teach "time rewind" without a wall of text?
Beat 1: Player fails a simple jump. Character falls into a soft pit.
Beat 2: A subtle ripple effect emanates from the character. Tap-to-rewind icon pulses.
Beat 3: Player taps. Time reverses cleanly. They see the path was always there, just obscured.
The Trade-Off: Visual Density vs. Readability
We pushed the dieselpunk aesthetic hard, but high-density visuals can overwhelm. Our solution: use animation itself as a guide. The "rewind" pulse is the brightest element on screen, forcing the eye. We sacrificed some environmental detail in the first level to prioritize this clarity. It's a constant tension.
Studio Ethos
Play First, Polish Second
"We don't polish a game until we've played it until it's fun. The first artifact is always ugly, but it must be joyful."
The Play-First Mandate
Core loop testing happens before any art is finalized. We prototype with programmer art to find the fun. If the core mechanic isn't engaging in a gray box test, no amount of visual polish will save it.
The Rule: We iterate on a feature for at least 50 internal play sessions before it enters the asset production pipeline. This protects our timeline from fundamental design pivots.
The Polish Layer
Once the core loop is solid, we apply our signature aesthetic. Polish is the final 20% of the timeline, but it defines the 100% of the player's memory. It's not decoration; it's psychological reinforcement of the fun you've already built.
Datreno Lexicon
- Core Loop
- The primary action a player repeats. Our opinion: If it's not fun in 30 seconds, it's not worth building.
- Developer Polish
- Optimizing code, memory, and build size. Our take: Invisible, but non-negotiable. A game that crashes is not a game.
- Feel Polish
- Juice, screen shake, sound design, animation curves. Our take: This is what makes a game "yours." We budget 15% of total time here.
- Surface Polish
- UI icons, menus, menu transitions. Our take: Essential for mobile, but often over-styled. Clarity > Character on screens.
Signature Module
The Integration Matrix
A decision guide to assess if Datreno's tech stack fits your project's constraints. Based on documented compatibility, not marketing claims.
| Engine / Stack | Mobile Build | Analytics | Monetization | Notes |
|---|---|---|---|---|
| Unity 2021 LTS | Optimized | Native SDK | Unity IAP | Requires manifest edit for Android 13+. |
| Unreal 5.1 | Optimized | Plugin | Native | Binary size is higher; focus on texture compression. |
| Godot 4.x | Beta | Manual | Custom | Experimental. No official SDKs. Build pipeline requires scripting. |
| Custom (Java/Kotlin) | Niche | N/A | N/A | Only for proven prototypes. Long-term maintenance risk. |
Decision Lens: What We Optimize For
Primary
- • Documentation clarity & stability
- • Impact on binary size
- • 60fps target on 5-year-old hardware
Secondary (Sacrifices)
- • Cross-platform feature parity
- • Cutting-edge graphics features
- • Rapid prototyping with 3rd-party assets
Boundary Conditions
- Assumption: Team size ≤ 3 for initial integration.
- Boundary: SDKs must not exceed 50MB total (iOS/Android).
- What Changes Our Mind: A documented performance regression >10% on target device.
From Warsaw to the World
A non-chronological capability mapFirst Title Released
"Arcadia Blues," a narrative puzzle game. Engine: Unity. Learned hard lessons about mobile build pipelines.
Tech: Unity 2019
Featured on Google Play
"Chrono Forge" selected for Indie Category. Team expanded to 12, adopting Unreal for specific projects.
Platform: iOS & Android
Toolchain & Methodology
⚛
Unity/Unreal
🔧
Perforce
🎨
Blender/Photoshop
📊
Firebase (Analytics)
⏱
Git for Non-Code
"Our build pipeline is non-negotiable. We automate testing on 5 physical devices (2 low-end Android, 2 mid-tier iOS, 1 tablet) before every publisher-facing release." — DevOps Lead, Datreno