Differences between gamedev and web app dev
So ever since february I am highly working on gamedevchallenge.org, which by the way has already gone private alpha.
That’s why I write actually. As the private alpha of the site already started, I got some good learnings in these early stages of that site. It might be obvious to some developers, maybe it should have been even obvious to myself, but somehow it wasn’t, so I learned this the hard, but good way.
Gamedev != Web app dev
Imagine that. For over a year now I am doing game development. Indie game development that is. As I do see a difference in approaching these developments to AAA titles.
So as an Indie game developer you usually just start with a prototype, at least that’s what I am doing. Mostly you already have something from the last game jam like Ludum Dare, or other jams, so you already jumped right into the whole experience of the game.
From then on you tweak and develop the hell out of the prototype until you got something you start to believe in. When you reach that point you polish even more, like crazy, until you get your game.
So the main approach just is to dive right in the work and let the things figure themselves out on the way. You don’t design too much, prepare architecture and map out every detail of functionality of your game before you even started to code one line.
Yeah, maybe a lot of people maybe do have this kind of approach, but it did not seem to work for me. I like to dive right in for games and just build things. As gamedev is mostly creative work, this seems to be a good approach actually.
Now web app dev on the other side, is a different approach. I should have known better actually, as I am a professional developer for a huge web application. I know the drill actually. But ever since having started out gamedev I saw a huge spike in productivity the indie gamedev way of programming. So I figured, why not try to go this same way for web applications?
Thus came gamedevchallenge.org
Yep, you know my project by now. This project just started. I read that indie gamedev bucket list by @clkwrk, had that idea and just dove into coding.
This went through for 3 months up to today where that private alpha just started and revealed a lot of problems in my design decissions.
Apparently without a major concept, a highly worked out design, a straight goal, your site is bound to become more or less a mess.
Things are not clear with the site, the design is too cluttered and complicated, and you just can’t see what’s going on in there. Also it is lacking so much features that it has become hard to even point out missing parts and just add on it.
So I have to restart the whole process, take two steps back and start planning and designing the application.
Why did it not work out? Because web applications just aren’t games. They follow their own rules, have totally different designs and need different skills to be done.
That’s why mostly you need different skills as a developer for web apps than as a developer for games. The former needs analytical knowledge and professional skills in software architecture, the latter needs a lot of maths and creative skills.
So is this thing burnt down now?
No way at all. I had a huge learning experience already with the project. Also I sure believe in that site. It does have potential to motivate a lot of people in fulfilling their goals. And that’s what I wanna do. Motivate and help people reach their dream goals.
I just have to take two steps back, rethink the whole design and work on that. And that’s what I will do. It just takes a while I’m afraid. That’s the downside to web app development I guess.