Thursday, February 9, 2012 In general, with games, this is what we’re trying to do. But in a more general sense, it’s about finding a solution to a problem, fast.
Thursday, February 9, 2012 In general, with games, this is what we’re trying to do. But in a more general sense, it’s about finding a solution to a problem, fast.
http://holtz.org/Library/Images/KnowingHumans/i%20think%20i%20can.jpg Thursday, February 9, 2012 Stop worrying! It’s just a prototype. Get over “blank page” anxiety and just start building. It’s ok to build something that sucks, that doesn’t work, or fails miserably...but you won’t know until you try. Just do it and move on to the next prototype!
Does this UI layout guide the user better? Can the HTML5 canvas render 200 images at once? Does this new layout, if it’s built in HTML5, using PHP and MySQL on the back-end, and running on IE6, get the user to buy more stuff? Thursday, February 9, 2012 Each prototype should explore one problem. It should have one goal. Multiple problems? Build multiple prototypes.
D. http://www.flickr.com/photos/kristiand/3223920178/ Thursday, February 9, 2012 Use whatever you’re most comfortable with: Flash, Unity, HTML5, your own engine, pen & paper. I have a prototype project for Xcode that I start with.
makejohnupyours http://www.flickr.com/photos/27448667@N05/3074676855/ ☑ ☒ Thursday, February 9, 2012 Don’t waste time building elegant, beautiful systems. Get ‘er done!
No Cookie Thursday, February 9, 2012 If the biggest open question is the AI following system, don’t spend all your time in the prototype on the graphics.