TECHNICAL
RESILIENCE.
Arcexa was founded in a small apartment in Istanbul with a single directive: solve the friction between ambitious game logic and the hard limits of mid-range mobile hardware. We don't just build apps; we architect digital infrastructure that survives the real world.
The Budget-First
Design Logic
Most studios start with "What looks cool?" We start with "What will it cost the user’s device?" In a market saturated with bloated software that drains battery life and devours data plans, Arcexa prioritizes lean, performant code.
Our origin story is rooted in the "Indie Budgeting Tool"—a prototype built by our founder to track asset licensing and microtransaction fees. That DNA remains. Every feature is a trade-off. If a visual effect costs 10 FPS on a three-year-old Android device, we pivot to a smarter optimization.
Terminology / Our View
- 01. Build Weight
- The total APK/IPA size. We believe anything over 50MB for a casual app is a failure of technical discipline.
- 02. Ethical Gating
- Monetization that respects the player. No loot boxes; our stance is that fair value loops yield higher long-term retention than high-pressure sales.
- 03. Thermal Ceiling
- The point where hardware throttles. We optimize to keep device temperatures low, extending both session length and battery health.
- 04. Maintenance Pledge
- Our 24-month critical fix guarantee. Abandon-ware is a plague on the industry; we stay committed post-launch.
Transparent Post-Mortems as a Studio Standard.
We publish our failures. After every release, we document exactly which cloud costs spiked, where our optimization fell short, and how we fixed it. Trust is built in the code, not the marketing.
Work with usTechnical Decision Lens
How we evaluate every line of code. Our framework prioritizes stability and acquisition over vanity metrics. Use this as a guide for your next development partner.
Evaluation Method
Our architecture is tested against high-latency regional scenarios (Istanbul/Ankara mobile nodes) to ensure robustness under fluctuating network conditions.
Logic over Layers
We optimize for CPU cycles first. Complex visual layers are secondary to core game loop responsiveness.
Battery Longevity
Applications must keep device thermals under 40°C during active gameplay to prevent user churn.
Minimal SDK Dependency
Every third-party integration is a potential bottleneck. We use custom lightweight modules whenever possible.
KVKK Compliance
Strict adherence to Turkish legal standards for user data handling and storage protocols.
Engineering Deep Work
Our Istanbul workspace is built for focus. We maintain a 'No-Meeting Wednesday' policy to ensure our developers can spend entire workdays in the "flow state," reducing errors and increasing build quality.
[Studio Coordinate: Harbiye Mah. Şişli]
System Constraints
- CORE: Unity 2024.1 stable release baseline for cross-platform parity.
- LATENCY: Maximum 150ms round-trip for server-side validation steps.
- ASSETS: Compressed textures via ASTC for all Android/iOS targets.
- LIMITS: No support for hardware older than OpenGL ES 3.0 to ensure minimum fidelity.
Questions Every Investor Should Ask
01. How does the app handle intermittent connectivity?
We implement local buffer systems that synchronize data once a stable signal is detected, preventing data loss.
02. What is the projected server cost at 50k DAU?
Our infrastructure scales horizontally using serverless edge computing to keep costs predictable on a per-user basis.
03. Can the asset pipeline adapt to brand changes?
Yes, our UI is built with dynamic templating engines, allowing for rapid skinning and localized content injection.