Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Learning objective c is a good option, but it's not the only option. </p> <p>If you are not a strong programmer, or if your focus is on being a good game designer rather than a good programmer (they are not mutually inclusive), than you might look into various middleware that can let you learn the basics of programming, without the challenge of learning objective-c simultaneously.</p> <p>There is a misconception that becoming a good objective-c programmer will make you a good game designer. What makes you a good game designer is making A LOT of games. So the faster you can get into making games, the better.</p> <p>Some good options that I use with my students:</p> <p><a href="http://gamesalad.com/" rel="nofollow" title="Game Salad">Game Salad</a> - Great for rapid prototyping, very easy to get into. Can be a frustrating if you want to do really complex stuff</p> <p><a href="http://stencyl.com" rel="nofollow">Stencyl</a> - More robust than game salad, allows "drag and drop" coding, or actual code. Also more complicated than Game Salad and not quite as intuitive.</p> <p><a href="http://coronalabs.com" rel="nofollow">Corona</a> - A true code based platform, working with the Lua language. Definitely more complex than the prior two, but probably easier to get into than objective-c and cocos.</p> <p>There are always going to be frustrations and limitations with these programs, but the trade off is speed.</p> <p>When it comes to getting started in game design, I recommend your first game be something very simple, preferably start with a known concept (in other words, clone something - its a good way to learn the basics). Once you have the hang of basic development and the different parts of game design, start to work on your own concepts, but keep it simple at first.</p> <p>Publishing a game on iOS is a whole other ball of wax, but the first step is making some games. Good luck, and drop a line if you need help. @happybadgers / happybadgers.com</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload