One approach that you can take to deal with this is to mentally back way the fuck off the 1990s on what your UI expectations are. Give up pixel-accuracy and fi

One approach that you can take to deal with this is to mentally back way the fuck off the 1990s on what your UI expectations are. Give up pixel-accuracy and fine-grained control of your app's UI layer, and just treat it how people like Peter Norvig and Chris Lattner treat their home pages. There isn't any browser with even 0.1% share that can't render those things. You also don't really have to go as far as those guys do, leaving the font 14-point Times New Roman and using HTML 1 tables. You can add some style, fonts, etc... just don't add anything that would make it _not work_ if somebody opened it in Netscape Navigator 4. There is definitely a big downside, in that your app won't look all dope and modern. For many apps that is a deal breaker. Also, some UIs really do require a higher fidelity UI. Not all UIs are just like, buttons and menus (although a lot are). But there is also a big upside: durability, in the sense that your app's UI will work on most 10-year old computers, and most computers 10 years from now.