After much work by the Learning Design team, we now start to see a structure of materials forming. This allows us to start creating a JSON document describing key attributes of each lesson and its associated activities.

This structure has also allowed us to create a custom build mechanism to ease UI modifications throughout the development lifecycle.

As well as aiding the development process, the same structure will be used to control the app when being used by a learner. Navigation of the lessons will be dynamically built at runtime. Learner progress will also be stored within the structure and stored to the user’s browser’s localStorage.

We are particularly keen to optimise the data recording the learner’s visits to each activity. This data could be used to dynamically evaluate the ease at which the learner finds each activity. If it appears the time a learner spends achieving a correct response is considered ‘quick’, we can suggest the learner may leap frog the more basic lessons.

As well as storing this data in the browser, the data could also be uploaded anonymously to a central server for more global evaluation.