Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
10_things_to_consider [2010/03/09 19:30] neurosky |
10_things_to_consider [2010/03/09 19:42] neurosky |
||
|---|---|---|---|
| Line 8: | Line 8: | ||
| 3. Consider the fact that everyone's ability will range. | 3. Consider the fact that everyone's ability will range. | ||
| + | Everyone is different. And that's exciting. You can create applications and programs that celebrate the difference between people to provide a more specific and customized experience. So, you should remember, that one size doesn't fit all, and that you should provide ways so that if one path is too frustrating, there should be other methods. | ||
| + | |||
| 4. Test it thoroughly. | 4. Test it thoroughly. | ||
| + | Make sure your program operates properly. Let other people try out the program and be open to feedback. Sure this is true about all development processes, but since there's such a "human" touch to brain wave input, then it is all the more important. | ||
| + | |||
| + | 5. Verify your logic. | ||
| + | Make certain that there are no logical loopholes that enable people to cheat the system. That's why utilizing the off head detector is useful towards gameplay. You should not freeze a meter at a given level if the MindSet is taken off of the head. Likewise, you would not want to enable a meter at 0 to equate towards a developmental buildup. Use all the information to provide logical gameplay. | ||
| + | |||
| + | 6. Utilize all the information. | ||
| + | The brain wave bands and raw output are useful towards creating additional environmental effects and mappings in your applications. Not everything needs to be a voluntary and direct control. Think about nuances and subtlety. | ||