Game Algorithm Development Program
Mobile gaming is a strange field. You can have beautiful graphics and compelling stories, but if your algorithms don't keep players engaged, none of it matters.
We've built this program around actual mobile game challenges. Not textbook scenarios — real optimization problems that affect player retention and game balance in production environments.
Starting October 2025, you'll work through six months of algorithm-focused development. We cover everything from matchmaking systems to difficulty curves, all within the context of mobile constraints.
How We Actually Teach This Stuff
We've tried the traditional lecture format. It doesn't work. So we changed everything.
Problem-First Learning
Each week starts with a broken game mechanic. You'll get a playable build where something feels off — maybe progression is too slow, or the difficulty spikes randomly. Your job is to identify the algorithmic issue and fix it.
Performance Analysis
Mobile devices have limited resources. We teach profiling from day one. You'll learn to spot performance bottlenecks before they crash your game on older devices. Battery drain analysis is part of every assignment.
Iterative Testing
You build, test with real users, collect data, and rebuild. We run small playtests every two weeks. The feedback can be harsh, but you'll learn what actually works versus what sounds good in theory.
Code Review Culture
Every algorithm you write gets reviewed by peers and instructors. We comment on everything — efficiency, readability, edge cases. Some students find this intense at first, but it mirrors actual development teams.
Platform Constraints
Mobile algorithms need different approaches than desktop solutions. We focus on battery efficiency, memory management, and network latency. Your algorithms must work on three-year-old devices, not just the latest hardware.
Data-Driven Design
Every algorithm decision should be backed by metrics. We teach analytics integration, A/B testing methodology, and how to interpret player behavior data. Gut feelings don't scale.
Who's Teaching This
Damien Kowalski
Algorithm Systems Lead
Damien spent eight years at a Barcelona mobile studio before he got tired of fixing the same algorithm mistakes in every project. He's worked on matchmaking systems for games with millions of concurrent players. His specialty is making complex systems perform well under terrible network conditions — which is most mobile networks, honestly.
Vera Ibáñez
Balance & Progression Expert
Vera has designed progression systems for fourteen mobile games. She approaches algorithm design from the player psychology angle — understanding how mathematical curves translate into player feelings. She's particularly good at explaining why small algorithmic changes can cause massive shifts in player behavior and retention patterns.
Six Months of Focused Development
Months 1-2: Foundation Systems
We start with random number generation, procedural content basics, and pathfinding algorithms. You'll implement A* for mobile, learn when to use greedy algorithms, and understand floating-point precision issues that break games.
Months 3-4: Player-Facing Algorithms
This phase covers matchmaking, difficulty adjustment, and loot distribution. You'll build systems that feel fair even when they're weighted. We discuss ethical considerations around engagement mechanics and where to draw boundaries.
Months 5-6: Optimization & Production
Final months focus on performance profiling, memory management, and preparing algorithms for production. You'll complete a portfolio project — a complete mobile game subsystem with full documentation. This is what you'll show potential employers.
Next Session Starts October 2025
We're accepting applications now for our autumn intake. The program runs October through March, with sessions three evenings per week and weekend lab time.
Program Duration: 24 weeks, part-time schedule
Time Commitment: 15-18 hours per week including lab work
Location: Barcelona campus with remote participation options
Prerequisites: Basic programming knowledge, mobile development experience helpful but not required