Examples:

The educational software I was prototyping for Scholastic is designed to have dynamic content based on a user's performance. The user's performance is sent to a server side application which then determines what content will be provided for future activities. Following are some activities that they decided not to use in the final software. These activities are set up to load their content from xml and load their assets from a folder, so that they would work with whatever content is fed to them by the server. For instance, the Word Building activity loads this xml file, l30-wordbuilding.xml. If you edited the list of words in that file the activity would use the altered list assuming the correct assets exist for the new list.

Note that these activities were designed to run locally (not from the web), if there is a lag in audio on your first run, try playing the activity a second time and everything should run smoothly as it loads from your browser cache.

Word Building

Word Tetris

Wack-A-Word

Alphabet Flow


Flex activities:

Assessment

Study Moment