Varuno Cidrex - Mobile Game Design
Designed by people who ship real games
The instructors here have released titles on the App Store and Google Play. That context shapes every session - not theory borrowed from textbooks, but decisions made under real constraints.
See who teaches hereCurrent conditions in the field
Mobile game design is not the same field it was four years ago
Touch interaction patterns, monetisation mechanics, and player retention loops have all shifted significantly. The program curriculum is reviewed each quarter - not as a formality, but because outdated instruction creates a real gap between what participants learn and what studios actually need. Sessions reference tools like Unity 2D, Figma for game UI, and Godot, which are in active use across the industry right now.
Where most people start - and where this goes
There is a specific distance between interest and capability
-
01
Most people arrive with an idea, not a system
Having a concept for a game is not the same as knowing how to structure its mechanics, pace its difficulty, or design its feedback loops. The program works on that gap directly.
-
02
Prototyping is where most self-taught designers stall
Moving from a sketch to a playable prototype requires decisions that tutorials rarely cover. Sessions address that transition with structured exercises and direct instructor input.
-
03
Platform constraints shape design more than most expect
Mobile means touch, small screens, interrupted sessions, and battery limits. Each of those factors changes how a game must be designed to actually work for players.
The hesitation most visitors carry
Time and prior experience - addressed plainly
Two questions come up more than any others before someone enrols. Both deserve a direct answer rather than reassurance.
-
What if I cannot commit 20 hours a week? The programme is structured for 6–8 hours weekly. Most participants hold jobs or study simultaneously. The recorded sessions mean you are not penalised for an irregular schedule.
-
Is prior coding or design experience required? No. The programme assumes curiosity and a willingness to work through confusion, not a portfolio. Participants with no prior design background have completed it and gone on to build their own projects.
What the programme involves
Format, duration, and access - enough to inform a real decision
Format
Live sessions with recorded access
Each session is delivered live with an instructor present. Recordings are available within 24 hours for participants who cannot attend in real time. There are no expiry dates on access.
Live
plus async access to all materials
Duration
Twelve weeks of structured instruction
The programme runs across twelve weeks. That is long enough to build something finished, short enough that the end remains visible from the start. Progress is cumulative - each week builds on the previous one.
12
weeks, one cohort at a time
Group size
Cohorts capped at a workable number
Each cohort runs with a maximum of 18 participants. That limit exists so instructors can give meaningful feedback rather than generic responses. It also means enrolment closes when capacity is reached.
18
participants per cohort, no exceptions
What the twelve weeks feel like from the inside
Not a syllabus - a description of how the experience unfolds
Weeks 1–2: orientation and environment
The opening sessions are deliberately slow. You configure your tools, establish your working habits, and get a clear picture of what the programme will and will not cover. Most participants find this phase less exciting than they expected - and more useful than they anticipated.
Unity 2D · Figma · Godot setupWeeks 3–6: mechanics and first prototype
This is where the work becomes uncomfortable in a productive way. You are building something playable for the first time, and the gap between what you imagined and what you can currently execute becomes visible. Instructors are present in this phase specifically because that gap needs guidance, not just encouragement.
Core loops · Touch input · PlaytestingWeeks 7–10: visual systems and UI
Designing for a small screen with a finger as the only input is a specific discipline. Sessions in this phase cover icon systems, feedback animations, and how visual hierarchy functions differently in games than in standard applications.
Mobile UI · Visual feedback · Icon designWeeks 11–12: submission and structured review
The final two weeks are spent finishing your project and presenting it to the cohort. Feedback is structured and specific - not a formality. Participants consistently describe this as the most valuable part of the programme, even when the feedback is difficult to hear.
Project submission · Peer review · Instructor critique
A note on pacing
The programme does not compress twelve weeks of work into eight. Deadlines exist, but the structure is designed to allow revision rather than penalise imperfection. The goal is a finished project you can actually show, not a rushed submission.
How the platform is regarded in its field
Associations and references that reflect the programme's standing
Referenced by regional design educators
Several university-level design programmes in western Ukraine have referenced the Varuno Cidrex curriculum when updating their own mobile design electives. That kind of influence is not something the platform sought - it reflects the specificity of what is taught here.
Participants have gone on to studio positions
A number of programme graduates have moved into junior and mid-level roles at mobile studios. This is not a guarantee the platform makes - it is a pattern that has emerged across cohorts since the programme stabilised in its current form.
Teodor Halvach
Lead Instructor, Varuno Cidrex
The measure I care about is whether participants can make something after the programme ends - not whether they passed an assessment during it.