The Belly Button Book
Ben Light
'The Belly Button' is an interactive children's book and set of wireless toys that extends beyond the page and allows curious 3 to 4 year olds to bring the story to life in their own bedroom.
http://www.bellybuttonbook.com
'The Belly Button' is an interactive children's book and set of wireless toys that extends beyond the page and allows curious 3 to 4 year olds to bring the story to life in their own bedroom.
The reader -- or child being read to -- can make parts of the story come alive. The child wears a toy button on their belly that when pressed, wirelessly activates strange things to occur in their own room.
One day a baby wakes with a button where her navel should be. Her obviously worried parents are compelled to press it. When the lights flicker in the book (press the button), a lamp flickers in the room. When the house shakes in the story (press the button), actual toys get knocked off of the shelves. When an elephant zips along in an airplane (press the button), elephant and jet sound effects are triggered.
This is a fun and magical experience for both child and parent.
Background
Read and break down children's books I would like to emulate, learn from them.
Test every stage of the story and prototypes on my nieces and nephews, get this in front of kids as often as possible.
The first few weeks I will create the story and illustrations. This includes: rough drafts, rough illustrations, character design, finished story, finished illustrations.
A few weeks dedicated to building the button: a wireless device that activates the "environment". I plan to experiment initially with Space Brew and node.js. The button will know where in the story the reader is, will be able to blink, make sounds, and activate wireless peripherals around the room.
A few weeks on the peripherals to create the experience: lamp flicker, toy shaker, sound effects, etc. The paper book itself will be a PComp device.
A few weeks on website, toy line, extras. These would be the expendable parts of the project, the nice to haves but not the necessary components.
A week to get the book actually self published, there will be a physical paper book at the end of the project.
Audience
3 to 4 year olds and their parents.
User Scenario
Story time. A parent reading to their child.
Implementation
The project is comprised of an illustrated children's book that wirelessly communicates with a toy button that controls wireless toys place around the room.
Conclusion
Children are the truest critics. If it doesn't work or they don't like something, they let you know. They will not spare your feelings. That said, when a child likes something, truly likes something, there is no doubt.
Making prototypes kid-proof is no easy task. An early round of kid testing, just to see how they break things, was very useful.
The reader -- or child being read to -- can make parts of the story come alive. The child wears a toy button on their belly that when pressed, wirelessly activates strange things to occur in their own room.
One day a baby wakes with a button where her navel should be. Her obviously worried parents are compelled to press it. When the lights flicker in the book (press the button), a lamp flickers in the room. When the house shakes in the story (press the button), actual toys get knocked off of the shelves. When an elephant zips along in an airplane (press the button), elephant and jet sound effects are triggered.
This is a fun and magical experience for both child and parent.
Background
Read and break down children's books I would like to emulate, learn from them.
Test every stage of the story and prototypes on my nieces and nephews, get this in front of kids as often as possible.
The first few weeks I will create the story and illustrations. This includes: rough drafts, rough illustrations, character design, finished story, finished illustrations.
A few weeks dedicated to building the button: a wireless device that activates the "environment". I plan to experiment initially with Space Brew and node.js. The button will know where in the story the reader is, will be able to blink, make sounds, and activate wireless peripherals around the room.
A few weeks on the peripherals to create the experience: lamp flicker, toy shaker, sound effects, etc. The paper book itself will be a PComp device.
A few weeks on website, toy line, extras. These would be the expendable parts of the project, the nice to haves but not the necessary components.
A week to get the book actually self published, there will be a physical paper book at the end of the project.
Audience
3 to 4 year olds and their parents.
User Scenario
Story time. A parent reading to their child.
Implementation
The project is comprised of an illustrated children's book that wirelessly communicates with a toy button that controls wireless toys place around the room.
Conclusion
Children are the truest critics. If it doesn't work or they don't like something, they let you know. They will not spare your feelings. That said, when a child likes something, truly likes something, there is no doubt.
Making prototypes kid-proof is no easy task. An early round of kid testing, just to see how they break things, was very useful.