P5

Trends In Kids Apps



Jobs And Roles

Concept - the basic, undeveloped idea of the game; a brief plan

Game design - the design, controls and mechanics of the game; deciding how everything works

Prototyping - making the first model of the game, used for testing and/or only developer use

Character design - how each character/avatar looks, talks, works etc; different functions or story relevance

Environment design - how each area/level in the game looks; are some areas going to be more interactive than others

Sound design - how the soundtrack/sound effects are made; different bg music for different areas, jingles for clearing a task

User interface - how the menus work, are they smooth/easy/functional; can you navigate the game easily, will it work for our target audience

Quality assurance - used to make sure the game is of the right standard/fits the guidelines; does it fit the target audience, are there any glitches to fix

Deployment - how the game is released, the advertising/launch date; is it releasing at the right time (June), what method should we use for advertising













Budget And Schedule








Legal And Ethical

Age ratings for games are decided by PEGI (Europe) and the ESRB (America). If our game was to be released, I think it would be an E 10+ (ESRB) and a 7 (PEGI) due to it's child friendly nature. Some themes, however, may somehow bump the PEGI rating up to a 12 as they are slightly more mature and not very common in kids games (eg Professor Layton is usually a PEGI 7, but some entries are a 12 due to certain topics they cover)

Comments