The Eric Wroolie Blog

Overpass Experiences

  • Blog
  • Videos
  • Overpass Apps

Powered by Overpass Apps

France and Germany say “No IE”—Corporate apps will suffer

January 19, 2010 by wroolie 2 Comments

So, Internet Explorer is in big trouble.  Both the France and Germany governments have called for web users to find an alternative browser this week this week.  Most tech-savvy users have already moved to Firefox and Chrome (I’m now completely using Chrome), but the majority of surfers still use the default IE.

Even more interesting, most corporate environments I’ve worked in support only Internet Explorer internally.  You are simply not allowed to install another browser.  I’ve worked on projects where the intranet application we are developing only works with Internet Explorer—usually because of bad coding/testing—but no one will fix this because “we only support Internet Explorer”.

I remember one high-level manager in an investment bank tell me—“Seriously, Eric, I can’t see us ever moving away from Internet Explorer.”

The lack of cross-browser support in the ASP.net developer community has been a big pet-peeve with me for years.  You don’t find this with PHP, Java, or Ruby guys.  But Microsoft developers stick with Microsoft browsers. 

I’ve had the arguments so many times in various contracts—“We should support Firefox too.  It only takes a few minutes to test functionality if we do it early enough, but will be a huge task to implement it later.”  I can remember having this argument a half-dozen times, at least.

It has never been easier to do cross-browser development (you should have tried it in the Netscape 3/IE 3 days—that was painful), but it still gets overlooked.

Even the online banking site for my  business bank account only renders properly in Internet Explorer.  This is a huge pain to go through all the necessary security logins for banking—only to realise you are in the wrong browser and you can’t read the page.  I’ve nearly changed banks because of this frustration.

An ideal web development team would have different developers using different browsers.  In a team of 4 people for example, have one person on each of the 4 major browsers—IE, FIrefox, Chrome and Safari.  Better yet, adhere to proper XHTML or HTML syntax (most of the time, apps only support IE because of some malformed html that Explorer allows). 

But for years I’ve heard the same argument from different people–“We don’t have that kind of time”, “It’s an internal application and the we only support Explorer”, and “We’re not a software house.  But now, when governments are recommending that we switch browsers, these developers haven’t even given their users this option.

This could kill Internet Explorer or at least severely weaken it.  I see a lot of “Make this website work in Firefox” projects coming up.

Filed Under: Software Dev & Productivity, Usability

Steve Krug Web usability video

January 8, 2010 by wroolie Leave a Comment

The best book I’ve read on website usability is “Don’t Make Me Think” by Steve Krug.  It’s pretty much considered the bible of web usability out there.  A very talented developer introduced me to it years ago and since then I’ve sent it to some of my clients.

I found the following video on the fantastic Signal vs Noise blog from 37 Signals.  It’s a one hour introduction to web usability given by Krug in 2008.  If you have a bit of time (I know an hour is a bit long), it really is an interesting talk so have watch.

The url for the video is (on Signal Vs Noise) is http://37signals.com/svn/posts/2092-i-cant-think-of-a-better-intro-to-the-essential

Filed Under: Software Dev & Productivity, Usability

In love with our own lingo

January 5, 2010 by wroolie 4 Comments

I worked on a software project recently where the interface was developed more by developers than end-users (you see this a lot, actually).  In this instance, the application needed a phone number (but not a mobile number).  Rather than asking for a land-line number (or just “Phone number”), the entry form asked for a PSTN.  I was doing a usability review of the app and pointed this out– “What the hell is a PSTN?”

The IT head pointed out to me that a PSTN is the industry term for a land-line (it stands for Public Switched Telephone Network) and that, now that I knew this, it should make sense to me.  I suggested he change it to “Phone Number”—since this app was going to be used by the general public.  He insisted that most people know this—just not me.  I told him he should still change it.  This advice fell on deaf ears, but we made some other good changes to improve the usability of the app.

I'm Not Sure What's Not Allowed
Creative Commons License photo credit: jakeliefer

My logic is (and continues to be)—if I don’t understand a term, it’s too confusing.  If I do understand it, would my grandmother?  In my situation, there are still occasions when I don’t understand something because of cultural differences– like expressions used in the UK but I never grew up with.  I still question them anyway.

This happens all the time—techies want to educate the non-techies on how to talk about technology.  Sometimes, these aren’t even terms in the technology industry—but acronyms and abbreviations used in a specific company that everyone adopts.  I’ve been in small twenty-person offices where you would think everyone went to school to learn how to talk like they do—even the secretaries: “Are you going to de-duplicate the NOC node or shall I?”  Eventually, no one knows how to talk like a regular person anymore.

We techies love our lingo.  In even smaller arenas (like a company or an industry) this lingo becomes even more precious. When we talk like this, we really sound like we know what we are talking about.  It impresses people (or so we think).  I can remember the feeling of working on a stock trading application for a major bank and talking about trade flips and different types of transactions and FSA systems and then stopping to reflect on how cool it must all sound—I was an insider.  I wasn’t a newbie—I sounded like an authority.

But all good software and hardware have the ability to take techie jargon and make it palatable to the masses.  A good site or web application should not imply when you log in that you have no business being there because you don’t know how to use it.  If you don’t understand the menu options, then you are in the wrong place.

In the future, people may look back at our gadgets today and conclude that Apple created the digital music player.  The truth was that portable MP3 players existed a few years before the iPod, but while techie ruled this area (with Rippers, LAME codecs, etc), Apple made the whole process simple for those who didn’t feel like pouring through thousands of forums and blogs to figure out who to rip a cd.  Try explaining to your grandmother how to set up a podcast aggregator while not using iTunes and you can see how much they simplified this area.  The term MP3 made it into the mainstream lexicon, but most of the terms of the early days did not.  Today, you still hear people argue about the benefit of Ogg or Flac over MP3, and can’t figure out why the mainstream hasn’t switched from MP3 to the superior Flac.  But the general public doesn’t care about this.

Google is revolutionary and I love the company, but to read many of the books out there (like “The Google Story” or “What would Google do?”) you would think that before Google, we were all randomly typing URLs into our browsers hoping to find something.  Yahoo, Ask Jeeves, Alta Vista, Lycos, etc were all there.  But Google made it easy in addition to being far more efficient.  One textbox, one button.  It was easy to tell your grandmother how to use it.

In technology, especially when it comes to interface design or anything that requires us to interact with the public, the best skill is to be a layperson.  Some people call this the “mother” test.  If your mother came to this site, or used your application, could she figure out how to use it without calling you?

I think about every time I have to fill in my tax forms how lost I am.  Even the “How to fill in this form” instructions confuse me.  It makes sense to someone, but they are in love with their lingo too.

Filed Under: Software Dev & Productivity

  • « Previous Page
  • 1
  • …
  • 7
  • 8
  • 9
  • 10
  • 11
  • …
  • 37
  • Next Page »

Recent Posts

  • My Gig and the Imposter Syndrome
  • Getting Picked Last for Teams in PE
  • One Little Growth Opportunity at a Time
  • I’m sorry if I look like I know what I’m doing
  • New Years Reclamations