Eonevolve Learning

Intent guide

How to Scope and Ship Your First Mobile Game

Skip the install-checklist fantasy. Scope a first mobile game by protecting one complete loop, cutting everything that needs its own tutorial, and shipping only when a stranger can finish one sitting without a coach.

Scope is a cut filter, not a feature list

Suitable first-game scope is the smallest product that still delivers one complete player fantasy. If you need a slide deck to explain the systems before someone can play, the scope is already too wide.

Use the matrix below as a review tool: lean columns describe a shippable first title; bloated columns describe a second product wearing a first-product costume.

Scope matrix

  • Player activityLean: One repeating verb the player can name in a sentenceBloated: Several modes that each need their own tutorial
  • Content volumeLean: Enough for a clear first session and one return visitBloated: A content roadmap that assumes months of live ops on day one
  • SystemsLean: One loop, one progression signal, optional light meta laterBloated: Economy, seasons, guilds, and crafting before the loop is fun
  • Team realityLean: Matches the hours you can actually ship in the next monthBloated: Assumes a full studio pipeline you do not have
Scope & Timeline Calculator

Mobile Game Idea & Scope Feasibility

Avoid months of abandoned development. Configure your core idea to see realistic timelines, risk factors, and MVP boundaries.

2 Verbs (e.g. Move + Aim + Cast)

Dangerous Scope Creep (High Abandonment Risk)

Cut 1 secondary mechanic or drop meta depth for MVP. Focus on proving the core verb first.

Estimated MVP Timeline14 Weeks (3.3 Months)

To a playable, polished vertical slice ready for internal playtesting.

Recommended Milestone Breakdown
  1. Week 1 - 2: Greybox prototype proving 1 core verb with hitstop & audio.
  2. Week 3 - 8: Level pacing & basic save loop.
  3. Final Stretch: Visual juice, 60 FPS mobile profiler pass, and app store build.

Name the one loop that must ship

Before features, name the repeating cycle: intent → action → result → re-entry. If that cycle is muddy, every later system will amplify the mud.

Your first-session job is not to showcase the whole game. It is to rehearse that loop until a new player wants another try of the same kind.

Core-loop mini diagram

A shippable first game needs a closed loop the player can name: intent, action, result, and re-entry of the same kind.

  1. Intent

    Player wants something specific in this moment.

  2. Action

    They spend attention on one available move.

  3. Result

    Something changes in a way they can notice.

  4. Re-entry

    They are invited back into the same kind of intent.

renewsRe-entry → Intent

A shippable first game needs a closed loop the player can name: intent, action, result, and re-entry of the same kind.

Reading order

  1. Intent

    Player wants something specific in this moment.

  2. Action

    They spend attention on one available move.

  3. Result

    Something changes in a way they can notice.

  4. Re-entry

    They are invited back into the same kind of intent.

Connections

  1. Intent → Action (commits)

    Intent without a clear available action is a wishlist, not a loop beat.

  2. Action → Result (produces)

    An action must leave a readable change or the player cannot learn the loop.

  3. Result → Re-entry (reveals)

    Result should invite re-entry of the same kind, not a different game.

  4. Re-entry → Intent (renews)

    Re-entry closes the loop only when it returns to another clear intent of the same kind.

Protect the loop with Keep / Cut / Later

Cutting is how a small team protects the loop. Write Keep / Cut / Later in public with your collaborators so half-built systems do not sneak back in.

Anything that needs its own tutorial before the main verb is taught is a Cut or Later by default.

Keep / Cut / Later

keep

  • One complete core loopIntent, action, result, and re-entry must work without coaching after the first teaching pass.
  • Readable first-session winA new player should succeed at the main verb early enough to want another try.

cut

  • Parallel modes at launchA second mode is a second product. Ship it only after the first loop earns trust.
  • Deep economy before a sitting budgetCurrencies and shops without a one-session plan create spreadsheet work, not fun.

later

  • Social and live eventsUseful after retention exists. Premature social systems hide a weak loop.
  • Cosmetic catalog breadthA small identity reward can wait until the loop is worth returning to.

A vertical slice is one honest sitting

A vertical slice is not a stack of unfinished systems. It is one thin path through the real product promise: start, play, feel a result, know what to do next.

Use the checklist when someone asks “are we ready to show this?” If you argue about the checklist wording, the slice is not ready yet.

Vertical-slice checklist

  • Promise is playableThe slice shows the fantasy you will sell, not a tech demo of systems.
  • Loop completes without crutchesA player can finish intent → action → result → re-entry without designer narration.
  • One sitting has a start and endYou can describe what a good session looks like in one sentence.
  • Known crash paths are closedThe slice survives a full sitting on your target low-end device class.
  • Cause reaches the next choiceOutcomes change what the player should try next, not only a score ticker.

A four-week sample production order

This order assumes a small team and a single primary verb. Stretch the weeks if you must, but do not reorder past “loop before meta.”

Week four is for ship readiness, not for inventing a new mode.

Four-week sample order

  1. Week 1

    Loop spike

    • Write the four beats of the core loop on one page
    • Build the smallest playable rehearse of that loop
    • Cut any feature that does not feed the loop

  2. Week 2

    First-session teaching

    • Teach notice → try → succeed → want-again without a meta tour
    • Lock controls and feedback timing for the main verb
    • Playtest with someone who has never seen the project

  3. Week 3

    Vertical slice

    • One sitting that represents the product promise end to end
    • Stable enough to survive a full session without known crash paths
    • One progression or reward signal that is readable, not decorative

  4. Week 4

    Ship readiness

    • Store listing and age rating path started
    • Performance and crash checklist closed for the slice devices
    • Cut list locked; later list parked without guilt

Three illustrative game ideas

Single-lane runner

Dodge and collect on one axis with rising pace.

Scope fit
High for a first ship: one verb, clear fail state.
Loop clarity
Intent and re-entry are obvious within seconds.
Cut risk
Temptation to add shops and seasons before the run feels good.

Board clear puzzle

Clear a small board with one match or merge rule.

Scope fit
High if levels are authored, not generated by a huge content pipeline.
Loop clarity
Strong if each clear teaches the next board pattern.
Cut risk
Meta layers and lives systems often arrive before boards are interesting.

Tiny city sim

Place and upgrade buildings with a soft currency.

Scope fit
Medium-low for a first ship: systems fan out quickly.
Loop clarity
Weak until the session budget and next decision are readable.
Cut risk
Economy and content volume explode before fun is proven.

Publishable checklist

Shipping is a decision, not a feeling. Close the list below for the slice you will put in front of strangers.

Ship checklist

  • Core loop named in one sentenceIf you cannot name it, players will not feel it.
  • First session teaches without a feature tourMenus wait until the loop has been rehearsed.
  • Cut list is written and acceptedLater features are parked with owners, not half-built in the build.
  • Vertical slice passes the readiness checklistPromise, loop, sitting, stability, feedback.
  • Store path is startedAccounts, age rating, and listing assets are not a surprise in week four.
  • Ownership of runtime reactions is explicitCritical feedback paths are not hidden in silent Update polling.

Continue into the graph

These guides and lessons deepen the decisions on this page. Each link includes why it matters next.

Related guides

Lesson link map

Browse all topics · All guides