Start Building

14-Day Game Development Challenge - Build and Publish Your First Game

You have two weeks. Your goal: build a small game and publish it so other people can play it. Not “almost done,” not “I’ll polish it later” — live on Itch.io or Steam by day 14. This challenge gives you a day-by-day structure so you actually ship.

Why 14 Days?

Two weeks is long enough to build something real (one core loop, a few levels or modes, a menu and a build) but short enough that you can’t hide behind scope creep. You have to choose one idea, cut everything else, and finish. The real win is shipping, not perfection. Once your first game is out there, the next one gets easier.

Before You Start - Lock Your Scope

Pick one thing your game is about. Examples: “collect 10 things and reach the exit,” “survive 5 waves,” “get the high score in 60 seconds.” No secondary modes, no “and also a story.” One clear objective.

Pick one platform. Itch.io is the fastest (no approval, free, instant). Steam is possible in 14 days if you already have a partner account and accept a minimal store page. For a first ship, Itch is usually the right call.

Pick an engine you know (or can learn in one day). Unity, Godot, or Unreal — or even a web stack. Use whatever you can already make a playable prototype in. Do not switch engines mid-challenge.

The 14-Day Schedule

Days 1–2: Concept and First Playable

  • Day 1: Write one paragraph: what the player does, what winning/losing looks like, and one “juicy” moment (e.g. a satisfying jump, a combo, a close call). Create the project, get input working, and get the player moving (or the core interaction working).
  • Day 2: Implement the core loop. If it’s “collect 10 and reach the exit,” make that work in one test level. No art polish yet — placeholders are fine. By end of day 2 you should be able to play from start to “win” or “lose.”

Checkpoint: Someone could play your game and understand the goal in 30 seconds.

Days 3–5: Content and Feel

  • Days 3–4: Add 3–5 levels (or equivalent content). Reuse one mechanic; vary layout or difficulty. Add one form of feedback: sound, screen shake, particles, or UI pop. Keep scope the same — no new mechanics.
  • Day 5: Playtest. Fix the top 3 bugs or confusion points. Add a simple main menu (Start, maybe Quit). Ensure the game runs full loop without crashing.

Checkpoint: The game has a beginning, a middle, and an end, and feels intentional.

Days 6–8: Polish and Build

  • Day 6: Add a simple options screen (volume, fullscreen if relevant). Improve one thing that felt bad in playtest (e.g. difficulty curve, controls).
  • Day 7: First full build. Export for your target platform (e.g. Windows/Mac/Linux for Itch). Test the build on your machine; fix any build-only bugs.
  • Day 8: Create a 30–60 second trailer or a short GIF plus 2–4 screenshots. Write a one-paragraph description and 3–5 bullet points for the store page. No novel — keep it short.

Checkpoint: You have a build and store assets. You are ready to publish.

Days 9–11: Store Page and Soft Launch

  • Day 9: Create your Itch.io (or Steam) page. Upload the build, description, screenshots, and trailer/GIF. Set price (free or pay-what-you-want is fine). Do not wait for “perfect” — publish as draft or unlisted if you want.
  • Day 10: Share the link with 5–10 people (friends, Discord, Twitter). Ask for one sentence of feedback. Fix one critical issue if something breaks or confuses everyone.
  • Day 11: Make the page public. Your game is live. Announce it in one or two places you’re comfortable with.

Checkpoint: The game is publicly playable. You have “shipped.”

Days 12–14: Learn and Document

  • Day 12: Read or watch one postmortem or “how I shipped” article from another indie. Note one thing you’ll do differently next time.
  • Day 13: Write a short postmortem for yourself (or for a blog): what went well, what you’d change, one lesson. Optional: post it.
  • Day 14: Rest or do one small improvement (e.g. a typo, one extra level). Do not start a new project yet — let this one sit. You finished the challenge.

Checkpoint: You have a shipped game and a clear takeaway for the next one.

Tips That Actually Help

  • Cut early. If a feature isn’t done by the day you planned, drop it or simplify it. Shipped with less is better than “almost” with more.
  • Build every day. Even a 15-minute session keeps the project in your head. One full day off is fine; two in a row and momentum drops.
  • Use free assets and placeholders. Sound, art, and UI can be generic. Focus on one clear mechanic and one clear win condition.
  • Itch first. No approval process, no fee. You can always put the same game on Steam later with a better page and more content.

What Counts as “Published”?

  • Itch.io: Game page is live, build is uploaded and downloadable, description and at least one image are up. Page can be unlisted at first; making it public counts as “published” for the challenge.
  • Steam: Build is uploaded, store page is live (or at least submitted and approved), and the game is available for purchase or as a free download. For 14 days, a very minimal store page is acceptable.

The point is that a stranger could find and play your game by the end of day 14.

Frequently Asked Questions

What if I miss a day? Shift the schedule. The order (core loop → content → polish → build → store → ship) matters more than the exact day. Finish by day 14 or 16; the habit of shipping matters more than the date.

Can I use AI or asset packs? Yes. Use whatever gets you to “playable and published” without blocking yourself. Credit assets and tools if required.

What if my game is “bad”? Ship it anyway. Your first shipped game is a learning project. The next one will be better because you finished this one.

Should I do Steam or Itch? For a first 14-day challenge, Itch is simpler and faster. Move to Steam when you’re ready for a longer cycle and store requirements.

What if I already have a half-finished project? You can use the challenge to finish and publish it. Lock scope to “one build, one store page, live by day 14” and drop everything else.

You do not need more time. You need a deadline and a plan. Use this 14-day structure, lock your scope, and ship. When it’s live, share it — and then use what you learned on the next one.

For more on shipping and publishing, see our game publishing guides and curated publishing resources. Bookmark this challenge and come back when you’re ready to run it.