Difference between revisions of "HTML5Demos"

From Lost In Wonderlands
Jump to: navigation, search
(See also)
(HTML5 Demos)
 
Line 1: Line 1:
 
= HTML5 Demos =
 
= HTML5 Demos =
 
''by paul.plaquette, Senior Software Engineer, Trilda Open Source''
 
  
 
'''NeXT Steps'''
 
'''NeXT Steps'''

Latest revision as of 16:32, 1 April 2017

HTML5 Demos

NeXT Steps

 here everything has yet to be done !

coming soon :

List nice pages using HTML5/CSS/JS Technologies


See also


HTML5 Demos

Audio/Video

 * cameara xylophone: http://www.soundstep.com/blog/experiments/jsdetection/


WegGL:


HTML5 Demos and Examples site


HTML5 blogs


HTML5 Performances

Note: By making it Fastbook Application Sencha has shown that one can build an application with performances but Sencha also demonstrated how the UX design can be tied to one platform performances.

Actually UX Design is also about taking advantage of strongnesses and avoiding weaknesses of one platform, but to achieve that UX design must work with Engineers else they would ignore about weakness and strongnesses inside a platform.

Sometimes it can also consist of not trying to design something that is simply impossible to implement on a given platform with correct performances or technically impossible.

Facebook wanted to keep its original web site based design, so browser based designed, using only one web page. In order to keep one single user experience so users would not be confuse.

Troubles in designing UX starts once we want to keep a single user experience across several platforms, without having took the time to consider weaknesses and strongnesses of each targeted platform.

Sencha in its Fastbook UX design uses several web views. Doing this they changed the UX Design with the benefit of having several web pages, that is, several web pages caches. By having several web page caches they can finely tune how they managed them, and how and when caches are reset. In doing this they can also keep a previous view state when they are re-showing it, while the Facebook application have to restore the whole view including re-downloading data.

This is also demonstrating how web page cache performance can be different from one platform to another - iOS is looking better than Android.

I tried the Fast book application on an iPad 1 and I did not found that the performance were so good comparing to the Facebook web site (the Facebook application is crashing...) - The iPAD 1 is having less RAM to operate and so it is less likely to be able to keep in memory several web page caches

This bring another aspect of UX design: witch platform are we targeting? What are their capabilities? Do we consider that an application have only to work on the more recent hardware? Do we consider we ant to keep some descendant compatibility?

Web Demo Catalog


Web App Demo Catalog

Web App for Web Browser

* sumopaint: http://www.sumopaint.com/www/
* WebInPaint: http://www.webinpaint.com/

Queecky: http://www.queeky.com/

  • Web Drawing:
* http://mudcu.be/sketchpad/
  • Web Paint and draw:
 * fatpaint: http://www.fatpaint.com/en/free_online_photo_editing_graphic_design_software/free-graphic-design-software-paint-draw-online-image-editor
  • Web Photo Editing:
* http://pixlr.com/editor/
  • Pearls Tree:
* http://www.pearltrees.com/#/N-u=1_88138&N-p=11724733&N-fa=977848&N-f=1_1656856&N-s=1_1656856
  • Adobe:
* PhotoShop : 
 * http://www.photoshop.com/
 * http://www.photoshop.com/tools

Web Games