Improve feel without expanding scope. Polish is clarity, not content.

The difference between a game that feels "meh" and a game that feels amazing is almost never a new feature. It's polish — tiny details that make everything feel alive. Watch what happens when you "juice" a simple game:

Video: Juice It or Lose It (15 min)

Martin Jonasson and Petri Purho take a boring Breakout clone and crank it up to eleven — live on stage. They add color, sound, screen shake, particles, and personality. The game mechanics never change. Only the feel changes. The result is jaw-dropping.

Discussion after watching: Which single change in the video made the biggest difference? Was it a new feature, or just a better version of something that already existed? What does "juicy" mean for YOUR game?

Polish means making existing things feel better — not adding new things. Smooth a movement speed. Improve spacing. Remove visual noise. Every change today should make the game feel more intentional.

Both games should address these:

  • Smooth movement speed — does movement feel right? Too fast? Too slow?
  • Consistent camera distance — camera should feel stable, not jarring
  • Remove remaining console spam — no console.log statements left in production code
  • Improve HUD layout spacing — text should be readable and well-positioned
Ami — Micro-Polish
  • Risk bar visualization (simple) — a visual indicator of current risk level
  • Clear "You are in Camp" indicator — the player should always know when they're safe
  • Boss encounter message distinct from regular encounters — boss fights should feel different immediately
Ida — Micro-Polish
  • Debt warning flashes at -40 — warn before bankruptcy at -50, not at the moment of failure
  • Clear "On Lot #X" label visible — the player should always know where they are
  • Car mode indicator visible when active — show that the car unlock is engaged

You need: A way to take screenshots (keyboard shortcut or Snipping Tool).

Step 1: Capture BEFORE.

  1. Open your game in the browser.
  2. Play for 30 seconds so it looks like a real play session.
  3. Take a screenshot. Save it as before.png. This is your baseline.

Step 2: Make exactly 3 small polish changes.

Pick three from this list (or invent your own):

  • Add a label that tells the player where they are
  • Change a color to improve readability
  • Add a visual indicator for an important state (risk level, debt warning, etc.)
  • Improve spacing or font size on the HUD
  • Remove something that creates visual clutter
  • Make a button or action more obvious

Step 3: Capture AFTER.

  1. Take another screenshot. Save it as after.png.
  2. Put them side by side. Can you see the difference?
  3. Show your sibling. Can they tell which is before and which is after?

The test: If someone can immediately tell which screenshot is "better" without you explaining — that's good polish. If they can't tell the difference, your changes were too subtle. Go bigger.
  • Make 3 small visual clarity improvements
  • Remove all remaining console.log spam
  • Adjust movement speed if it feels wrong
  • Improve HUD readability
  • Test: game feels intentional not accidental
  • Ask someone to play — do they understand without explanation?
    •
    Checkpoint

    Game feels intentional, not accidental. Small changes create big feel improvements.

    No new mechanics. No new areas. No new features. Visual clarity only.

    "While I'm polishing, I'll just add..." — NO. Polish is refinement of what exists. Adding anything new is not polish.

    Polishing code that works but looks ugly — refactoring is not polish. If the code works, leave it alone.

    Spending too long on one detail — three small improvements beat one perfect one. Move fast.

    This lesson teaches taste. Polish is about noticing what feels wrong and making it right. It's subjective, and that's okay.

    Ask: "What small change improved the feel the most?" Often the smallest changes have the biggest impact. A label, a color, a timing adjustment.

    The Before & After activity is powerful. Seeing improvement side-by-side builds confidence. Save both screenshots — they make great "portfolio" evidence of growth.

    Watch for scope creep. "Polish" can easily become "adding new features." If they say "I want to add a minimap for polish" — that's a feature, not polish. Polish improves what exists. A minimap is new.

    Tomorrow: We FREEZE. No more changes. The code locks. Tomorrow is the last day you touch the code — and only to clean it up, not to add anything.