01
The studio
An independent team building small, complete games.
1Who we are
Alizey Developer is an independent game studio working exclusively in the hyper-casual space. We build lightweight titles for mobile — the kind of game you open while waiting for a bus, finish a round of, and put away again.
We are deliberately small and deliberately narrow. Instead of spreading across genres, we focus on one thing: making short-session games that are instantly readable and satisfying to repeat.
2What we care about
- Clarity over complexity. If a player needs instructions, the design is not finished yet.
- Respect for time. A session should feel complete in under three minutes.
- Honest difficulty. When a player fails, it should be obvious why.
- Small and finished. We would rather ship something tight than something oversized and half-polished.
02
What we make
The shape of an Alizey game, described without a title.
1The format
Every project starts from a single mechanic and stays close to it. Rather than stacking systems, we explore how far one idea can stretch before it stops being fun.
- One mechanic per game. The rule is taught by playing, not by a pop-up.
- One-thumb control. Designed for portrait screens and a single hand.
- Rounds measured in seconds. Short loops with a fast path back into play.
- Light footprint. Small downloads, quick cold starts, low device requirements.
2What we deliberately avoid
Hyper-casual does not have to mean careless. There are patterns we choose not to build around.
No forced tutorials
If a screen needs a diagram to explain, it gets redesigned instead.
No interruptions mid-run
Monetisation slots sit between sessions, not inside the core loop.
No inflated scope
Features that do not serve the loop get cut before release.
No heavy requirements
Older hardware is part of the target, not an afterthought.
04
How we build
A short loop, repeated until the game is worth keeping.
1The process
-
Prototype the core.
A grey-box build with placeholder art, built to answer one question: does the mechanic feel good on its own?
-
Test the feel.
Tuning input response, camera behaviour and difficulty curve before anything else is added.
-
Put it in front of players early.
Real sessions with real people, observed rather than surveyed.
-
Decide with data.
Early retention and session behaviour tell us whether to continue, adjust or stop.
-
Polish the edges.
Load time, frame stability, layout on smaller screens and first-launch experience.
-
Ship, watch, iterate.
Release, measure, and make focused changes rather than large rewrites.
2Working in small cycles
We keep production cycles short on purpose. A concept that cannot demonstrate its core loop quickly is a concept we would rather abandon than carry forward — killing ideas early is cheaper than polishing the wrong one.
The same applies after launch: changes stay small and measurable, so we always know which adjustment produced which result.
06
Working with us
For publishers, ad partners and storefronts.
1What we are open to
- Publishing partnerships. Distribution support for finished titles.
- Advertising networks. Integration discussions around between-session placements.
- Localisation. Collaborations on store listings and in-game text.
- Creative production. Support on store assets and short-form promotional material.
We keep the scope of partnerships narrow and the terms clear. If you are unsure whether something fits, ask — a short email is enough to find out.