My man Hamish Todd was recently asking me about something I told him some time back; I told him that in game development, I polish as I go. I wanted to elaborate on that since it's a useful, but complex production style. Readers of this blog and followers of my game combat philosophies have heard me say that I developed one attack at the very beginning of Aztez, and didn't move on to another attack until that one looked and felt great. But other game developers could argue that polish is of secondary importance, and that the rules systems and mechanics are the most important thing to nail down first. And this is where I disagree!
(This is an image from a mech strategy game currently being developed by Zach Fowler. When he made this image the prototype was a mere 3 weeks in development! How jazzed did you get just looking at this?!)
Now I understand you can't have a game without rules and goals and interactions/mechanics, but only a certain percentage of the fun lies in the systems themselves, while the rest is derived from the polish. I'm not specifying an exact percentage because it completely depends on the game type. But the point is, it's most certainly not 0%! Things like scenery, effects, enjoyable and clear UI, stimulating audio, etc...all these things are massive part of the package. Now this is common sense to most people, but why do it from the start?
(That is the first attack prototype I ever did. This boned me up, and boned up everyone I showed. And this was mere moments into development. Push Z to attack.)
I think it's important to do it from the start because one of the most important phases of game development is at the beginning, when a dev is just beginning to bring a burgeoning idea to life. They should be determining if an idea is worth pursuing, and put it down if it's not. A critical part of this process is involving players; at first, friends and family, and then later, unbiased strangers. Their feedback is instrumental! And you've got a much bigger chance of lighting up their brain if there's some polish there! The clearer an idea you can provide them of what the game looks like when it's done, the better. With that being said, let's talk about Kyle Pulver for a moment.
You've probably heard of his games or seen his work at some point. What you might not know about him is that he is a regular and fierce game jam participant, and he has racked up more "Best Of Jam" medals than anyone I've ever known or heard of. While he's generally brilliant and highly agile by default, he does this overpowered nonsense where he polishes the shit out of his game jam creations. Looking at one of his 2 day creations is thrilling, and anyone who sees it gets super pumped up! There's obviously a huge advantage there in terms of "early marketing", but the truth about Kyle (and everyone else who polishes as they go) is that they do it to excite themselves! When you have to experience the interactions you've designed a BILLION fucking times as you go, it helps to make sure these interactions look and feel good.
Anyway, this style of development is by no means critical. But you're just doing your game a massive disservice by not making it sexy from the start. Allow it to produce its own inertia and drive development! If your developer brain doesn't naturally go here but you want to make it happen, then get involved with an artist whose very purpose is to make games sexy. Let them do their thing! Even if you don't think your own short-term excitement is critical, the short to long term excitement of potential players IS, and you can't argue with this.