Tech Assessment

Abstract

        We will be building our game using Sprite Kit, a new game-development framework released by Apple in iOS 7.  We will be building our game from scratch rather than modifying or maintaining an existing one.  The most critical limiting factor to what we can accomplish with our given tech stack and goals is the amount of time each team member will be able to contribute over the 10 week period during which we will be developing the game.  With each decision we’ve made, we have struck a balance between what we hope to accomplish in this limited time and what we reasonably believe we can.

Tech Stack

        iOS7 - With iOS7, we are able to use SpriteKit, a new framework for 2D games that Apple has released as part of its native libraries.  We have reason to believe that SpriteKit will take cocos2D’s place as the best 2D-game framework for iOS.  In addition to its native physics and particle engine, SpriteKit’s documentation and maintenance is done by Apple, which is evidenced by the fact that its documentation now is more complete and readable than cocos2D’s.

        Sketch - Sketch will make it easy for our artists to create vector graphics.  Vector graphics can be scaled to any pixel count and still look good, which is important when we consider the slightly different screen sizes of iPads.

        Github - Github is a reliable way to store and share our code.

        Google Docs - Google Docs is a reliable way to store and share our documents.

Team Qualifications / Specialties

        Art - The art of the game will be managed by Eoin and Bryan.  They have some skill in this area already.  More importantly, they have interest in this area.

        Complexity Management - The team will work together to separate classes, scenes, and logic so that the game’s many pieces fit together well.

        Game Design / Sprite Kit - John and Bryan will be building most of the game logic as the project’s “code monkeys.”

        Product Management - Eoin will manage the team, set goals for sprints, and decide on the group’s directions. 

Expected TimeScale of Checkpoints

        Alpha Build (4 weeks from coding start)

        Beta Build (4 weeks from Alpha)

        Stretch Goal (?)