Business benefit of ensuring fit for purpose presentation layer

Posted by | Ideation | No Comments

“What exactly is the business benefit of doing that?”, a cry oft heard.

Well, what exact business benefit is there for not ensuring the presentation layer is ‘fit for purpose’? To build a “web” based application meeting all specific requirements and policies in regards scalability and the like – then ignoring its output “just because” it does what it does and appears on the surface to render as it should …. ?

Following modern techniques, ensuring your presentation layer is split against semantic markup and seperate styling gives the ability to alter the way an applications output looks and feels merely through editing CSS stylesheets in the presentation layer. Business benefit? You don’t have to raise the same level of change requests and prioritise development work to back-end developers nor do you have to ensure you’re within a release schedule several months away – where the focus will be on ensuring business layer upgrades requested by the business take first priority! Nor is there a need to edit deep down in the business layer at what are most likely multiple points to alter inline styling.

A benefical frontend development strategy creating real cost savings

Why? Because, it can be done by front-end developers and can be done in a fast turnaround with next to no cost leaving backend developers prioritising and developing workstreams providing “real” long term business benefit without wasting precious effort and time! User interfaces can be improved/tweaked adhoc providing end-user centric benefits when required without conflicting with underlying business logic or data storage.

For instance, improving end-user input through user experience (UX) best practices without additional requirements of backend development and or error-checking and processing by simply altering the user interface can pay dividends further downstream! Improved data quality and removing the need to re-key information or use generally poor scrub & match automation delivers on-the-ground business benefits through no cost. The only definite requirement is to ensure alignment of a presentation level release schedule fitting with programmatic releases if required; or seperate them completely!

Making certain frontend web industry standards are applied is a forward planning strategy producing real cost and time savings!

First published on yaduk on Apr 30, 2009

Internet Explorer 6 is not yet dead! IE6 is alive!

Posted by | Ideation | No Comments

You’d be absolutely amazed at how many people are still using Internet Explorer 6! One of the hardest things I’ve had to explain is this very thing; some people just don’t comprehend anyone can be on anything less as the latest bleeding edge browser since they are!

There are however, many companies still using this very browser, not least due to the massive undertaking that it might be for them to upgrade away from it. For instance, think mission critical legacy applications working fine right now – how can senior colleagues be assured they’ll still work as intended after any upgrade? Long lengthy expensive test plans and presentation layer upgrades prior to any painful upgrade most likely.

Think then of the vast swaith of potential website users sitting in offices browsing the web in their lunch hour being discriminated against?

Should Internet Explorer 6 not be part of your ‘progressive’ web development you’re quite probably damaging your own clients revenue potential! Not sure they’d like that if they knew ;)

First published on yaduk on Nov 19, 2009


I myself have begun to narrow my view of IE6. Though there are still many coporporate environments with Microsoft support contracts to enable them to still use IE6 – HTML5 and the vast swaith of exciting things that can now be achieved with modern browsers HTML5/CSS3/Javascript means supporting decrepit browsers is nothing more than a chore.

So what’s this site do? IE6 / IE7 you get the default skin. Any other browser … this skin!