Aus meinem Intranet-Blog und deswegen auch in englischer Sprache.
I’d like to point out what a true web app has to look like and especially what not! […]
DOs & DONTs
- don’t use proprietary “de-facto”-standards like Flash, ActiveX
- don’t use browser plugin driven technology, especially HTML5 renders many plugins obsolete
- do drive your back end by well known engines that perform and scale well, e.g. Apache2, PHP(5.3), MySQL, PostgreSQL
- don’t restrict clients/users by choice of browser technology, like Internet Explorer Only, WebKit Only, Gecko Only
- don’t restrict clients/users by choice of OS technology, Windows, Linux, OSX, (think PORTABLE DEVICES!)
- don’t try to circumvent the above by relying solely on JAVA platform
- don’t enforce specific JAVA version. If you can’t, don’t run JAVA at all
- don’t encourage support of obsolete/legacy browser technology, e.g. Internet Explorer Series 6 and below
- do provied WEB API with your WEB App, e.g. RSS, Atom, JSON, REST
- do make usability your top priority for client/user experience
- don’t get to fancy about style. In a productive environment mostly stick to platform defaults
- don’t anticipate any minimum screen size. YES, desktop screens mostly offer somthing larger than 1024×768. NO portable devices don’t!
- do provide same functionality with different layout for different screen estates. (size, orientation)
If you need technical support by a 3rd party for any cornerstone of your true web app, it’s highly likely you bet on the wrong horse.
If you want to create something new fashioned, don’t use/support old fashioned tools. For example Internet Explorer 5 is from 1999. This bad boy is more than 10 years old and thus has no reason to be supported at all! IE6 is close on it’s heels (2001).
If something style related is not fully supported on every target platform (think PNG with alpha channel/transparency) it’s low priority but if something usability related is no supported by target platforms MAKE IT WORK.
to be continued…