"Looks Done, Isn't Done": Our Polish-First Indie Mistake
"Looks Done, Isn’t Done": Our Polish-First Indie Mistake
Open the Wayline editors — pixel sprites, sheets, palettes, scenes — and export drop-in assets for Unity, Unreal, and Godot. Free to start, no signup.
We almost shipped a pretty, hollow shell. It’s a cautionary tale, and one I hope helps you avoid the same mistake we made.
We jumped headfirst into art. Shiny textures, detailed models, custom animations - the works. We were building a visually stunning world. We thought that’s what players wanted.
We were wrong.
The Allure of Visual Polish
It’s tempting. Polished visuals grab attention. They look professional. They feel like progress.
We got positive feedback early on. People saw screenshots and were impressed. This reinforced our belief that we were on the right track.
The problem is, visual polish is a surface-level investment. It hides fundamental flaws.
Our “Polish-First” Nightmare
Our game was a strategy RPG. We spent months creating character models, environments, and special effects. We had beautiful landscapes and intricately designed units.
But the core gameplay was… lacking.
Combat was slow and repetitive. The AI was predictable. The strategic choices were limited.
We were so focused on making it look good that we forgot to make it fun.
The Scope Creep Trap
Investing heavily in art early created a sense of sunk cost. We had to use those assets, right? This led to scope creep.
We added features just to justify existing art. A new character model meant creating a new skill tree, abilities, and animations. This took time and resources away from fixing the core gameplay issues.
Each new feature added complexity. It made it harder to iterate on the fundamentals.
The Feature Lockdown Fallacy
Our beautiful assets created a sense of feature lockdown. We hesitated to make significant changes to the core mechanics. We didn’t want to invalidate the art we had already created.
This was a major mistake. We were afraid to experiment and take risks. We were stuck with a mediocre gameplay loop because we had already invested so much in its visual representation.
Wasted Art Assets
Eventually, we realized the core gameplay just wasn’t working. We had to make drastic changes.
Some of our beautiful art became obsolete. A character we spent weeks modeling and animating was removed from the game entirely. Environments were redesigned to better support the new gameplay mechanics.
All that time and effort poured into those initial assets felt like a complete waste.
A Better Approach: Gameplay First
We learned our lesson the hard way. Now, we follow a “gameplay-first” approach.
Functional Prototype: Start with a simple prototype. Use placeholder art. Focus on getting the core mechanics working.
Iterate, Iterate, Iterate: Playtest the prototype. Gather feedback. Make changes. Repeat until the gameplay is fun and engaging.
Progressive Polish: Once the gameplay is solid, then start adding polish. Focus on the areas that will have the biggest impact on the player experience.
Evaluating Polish Needs
How do you know when polish is truly needed?
- Does it enhance the core gameplay? If polish makes the game more fun, engaging, or intuitive, it’s worth doing.
- Does it address a specific problem? If polish fixes a visual bug, improves readability, or enhances performance, it’s a good investment.
- Is it cost-effective? Consider the time and resources required for polish versus the potential benefits.
If the polish is just for “window dressing” or to impress others, it’s probably a distraction.
Task Prioritization: Gameplay over Graphics
Prioritize tasks based on their impact on the core gameplay.
- High Priority: Core mechanics, AI, player controls, level design.
- Medium Priority: UI/UX, sound effects, music.
- Low Priority: Detailed character models, advanced visual effects, environmental decorations.
It’s okay to have placeholder art for a long time. Focus on making the game feel good before making it look good.
Scope Management: Kill Your Darlings
Be ruthless with scope. Cut features that don’t contribute to the core gameplay. Don’t be afraid to “kill your darlings” - even if you spent a lot of time creating them.
A smaller, well-polished game is better than a large, buggy, and unfocused one.
Actionable Advice: Start Small, Iterate Often
Start with a small, manageable prototype.
Get it in front of players as soon as possible.
Gather feedback and iterate based on what you learn.
Don’t be afraid to experiment and take risks.
Focus on making the core gameplay fun and engaging.
Only add polish when it’s truly needed.
Embracing a “Gameplay-First” Philosophy
Adopting a “gameplay-first” philosophy requires a shift in mindset. It means prioritizing function over form. It means being willing to sacrifice visual polish for the sake of better gameplay.
It’s not always easy. But it’s the best way to create a successful indie game.
We nearly crashed and burned prioritizing art. Learn from our mistakes. Focus on the fun, and the visuals will follow. Your game will be better for it.