Although I haven’t written the talked about application myself I am a developer at SEB and I just feel I need to defend some of the critique.nnBuilding a public bank application is not really the normal use-case one would meet every day. There are a million things to take into concideration, maybe 10% which relates to GUI. Choices and prioritation comes into play because it is such a large business case. Even if some of our customers find it to be a “no brainer” we have alot of improvements planned and done that maybe relates to security and transactions rather than if we use frames or not.nnI know there is a lot of hype around building “proper” web sites and latelly there seems to be some sort of movement going around and finding what is wrong with each and every site. One have to remember however that some things, take frames, works – even if it is not “standard” or “the right way”. Many times we have to way what it would cost to re-design the entire front end against what we actually gain from it. Let’s say we spend 10 million SEK on fixing the proper syntax, but keeping the same Look and Feel, we have to ask ourselves – are we getting those 10 million back? Will all of our customers check the HTML source and do more transactions? Will people over at Skandia banken choose SEB instead because of the syntax?nnThe short answer is No.nnUX and Usability (the “helping” feature i.e.) is something that might be of more value today however. Making it easy for our customers will actually work against mentioned goals. But this is when budget and previous versions of the application comes into play. Historically, the feature you are talking about was actually a request by most of our customers. People wanted to skip using tabs because they found it not so clear. Remember, our customers are not only computer wizards who sit infront of the computer 24/7, we have a few mothers, fathers, corporations, handicaped etc. in our demographic.nAnyway, changing this behaviour might be motivated but you still have to compare it with other project that might have a larger business case and goal. Even if it seems to be a simple thing to do (just re-write the source) we have to fund it, staff it, run it as a project, go through all types of tests etc. etc.nnNow, never fear. We are actually building a new front (and back) so some of the requested changes are coming. But one has to remember that we are also bound by certain legacy systems, technical platforms and all types of paramters that might force us to do some things in a “sluggish” way. You always have to compromize if you are trying to serve everyone while still maintaining somewhat old technologies which cost alot of money to upgrade from.nnHej Markus =)