Before starting to generate the application contents and with the aim of improving the best service, several pending points have to be solved and a development model has to be produced to make the creation of contents more dynamic. In general, the following steps need to be regarded:

• Image vectorization: in order to reduce the bandwidth usage, gain flexibility and improve the performance, it is necessary to make use of vector versions of the images. These versions are based on lines and points, instead of pixmaps, and not only do they take up less space, but they also allow to use more visual effects.
• Performance: It has been noticed that animations may stall when a high resolution is used. One of the first goals now is checking whether the situation could be improved with vector graphics, as well as knowing the complexity the browsers could endure in that case and, if it is not possible to run it successfully in high quality, search a resolution in which the animation can work properly.
• Compatibility: initially, the application is supposed to be executed with SVG, the standard vector graphics in the Web. Unfortunately, although it is successfully held by other browsers, it will not work perfectly well with Internet Explorer until IE9. It is probable that, in such a case, we should make use of Flash to replace it. It is necessary to find a way of doing so without causing too much trouble.
• Music and audio: we have to check HTML5 features to reproduce audio as part of the animation. As an alternative to IE8 and lower, a new use of Flash is being considered.
• Tool development: Both the vectorization and the subsequent animation (and creation of activities) are tasks that may take long. In order to add contents quickly and make the work easier, it will be desirable to develop our own tools.

This has been a summary of what is left to do before continuing with the content development. We would like to finish it all by April and launch the final application this month.