This page is from our blog archive
You may still find this page interesting, but there are more relevant and up-to-date blog posts available. Use search or filter options to find the latest content.
This is the gap that Adobe Flex/Flash and Silverlight have filled in the past. They’ve allowed developers to stick with familiar environments when making browser-based applications in the enterprise.
Many more developers don’t have direct experience of developing graphical applications. When graphical components are done right they can look deceptively simple to code. It can easy to underestimate the effort needed when positioning pixels precisely, designing animations, exact hit-testing, writing dragging code & eeking out the best performance on a range of browsers.
Project managers and system integrators like to keep their development costs under control. The last thing they need is an over-confident developer who spends a year developing something that it would be easier to just buy in.
Managing risk is critical. Buying an off-the-shelf component with a well-defined function in the project is less risky than developing it from scratch because it can be evaluated & assessed beforehand. The evaluation can be built into the project plans. And once the project is complete the visualization part of the stack will be supported on proper commercial terms, long after the development team has moved on to other things.
OK, that is the hard sell over. For now…
In our next posting we’ll blog about the how browser-based visualizations have been made over the years, from Java to Silverlight and beyond.