You could also request the http info and simply show that to a person on a page. In rails it would be as simple as calling 'request.user_agent' and printing that value on screen.
Needed a branded version? This is when you're talking to clients that can't tell the difference between one browser and another? These clients can't tell the difference between a big blue e, a fox or a colourful circle? Yet you needed a branded version?
I'm just pulling your leg, I understand that you needed a branded version and that wasn't influenced by your clients inability to distinguish between core brands in the online space.
Thanks for letting me know. I'll not be rushing out to add hexagonal.js to my Rails app, but if one of my friends who likes js wants to try building their own full app I'll mention this as a possibility.
How can it be a good thing to follow the MVC framework on both the client side and the server side, as it says in it's philosophy, when the client side is the V in MVC?