It constantly amazes me how many AIR apps have taken the time to make custom chrome that looks nearly like a normal window, except for the color, or a little shine.  I’ll admit I’ve been guilty of it too.  My first couple of air apps had fancy styled and skinned chrome too.  I was charmed by the fact that I could make it look however I want, the ultimate control I thought.  Then I sat down and started thinking about it more seriously.

From my point of view there are two primary problems with custom chrome.  First, it doesn’t look like it belongs on the system.  Worse, it usually means that  the close/maximize/etc. buttons are on the wrong side on some systems.  The second issue is the effort that goes into it.  Unless there’s a compelling reason to break from the OS look, don’t do it. Windows already look like windows, plus they match whatever system they are run on.  Don’t give in to gratuitous custom chrome.

Not that there isn’t a place for this functionality.  Small widget-like apps can pull it off quite nicely.  They’re expected to look a little different.  I’m sure there are other use-cases where this makes sense too, where the default window is just too limiting.  Think it through first though, if all you need is a standard window to hold your application, then use it.  The work has already been done for you.

This entry was posted on Tuesday, April 1st, 2008 at 3:17 pm and is filed under General.