The demos should serve different audiences and purposes:
- Stakeholders and potential users
- CLOUD4All/GPII funders
- Potential participants and collaborators
- To make the concepts easier to understand.
- To show progress as more elements are developed. Demos should be connected to whatever we do for a "Living Roadmap".
- To give stakeholders something concrete to respond to, as part of the ongoing R&D. It'll be easier to get useful answers to design questions if we can show people our current thoughts about how it should work. True for AT vendors, users, educators, etc.
- To gather more interest and support, and active participation from potential collaborators and contributors
These are at events, conferences, etc. Someone is at an exhibit booth to explain the demos, walk the visitor through them, etc. (Although we have discussed the idea of remotely supporting demos via a call center such as the one envisioned by AssistMeLive.) These demos should be accompanied by attractive exhibit hardware and furniture. There might be some form of script. When the demo is taking place at a venue not closely associated with CLOUD4All/GPII, there should be an attempt to interpret the demo in 'local' terms. For example, if it's at an educational technology conference, both the content of the demo and the 'patter' should be crafted for that audience -- show classroom materials, student personas, etc.
These demos would be performed by interested persons at their convenience, 'in the wild'. They might have to be pretty constrained as to functionality and duration. They might need to be scheduled, and require a registered user account. They could be permitted only during limited hours, and have some support. The advantage of having these demos is that it allows more viral activity, especially if we design and document them right and disseminate their availability.
If they use listeners (instead of simulating real use by logging in somehow), the types of listeners should reflect the technologies widely available -- cameras, USB ports, rather than NFC for now.