In all seriousness, I'm going to slow down on drawing out Chapter Five's beats and switch gears to think about my interface and how it behaves. This is critical, as when I'm done, I should have all the pieces necessary to create a product requirements document. Ugh sounds so business... But it's necessary - you can't just code without a plan. Just like writing a story, if you don't have a roadmap, it's going to end up a jumbled, tangled mess. Except it'll also be filled with game-killing bugs. Hooray?
The PRD is going to define pretty much everything the game needs to have, from the systems to the variables and the logic in between. Since this is destined for mobile, I have to think about how you'll be interacting with your phone to move the story forward. Do you prefer to tap links or swipe the screen? Do you want expanding menus, or do you want everything always available? Do you want sound effects? Music? Do you want a customizable color palette? Or will a simple day mode vs night mode suffice? Do you want flowery, snappy, or witty prose, or would you prefer something more subdued and easier to read?
There are lots of things to think about in terms of how you absorb the story, and all of them should be intuitive, interesting, informative, and above all: entertaining.
Wireframes incoming - stay tuned!
Wireframes incoming - stay tuned!
