Re:Nokia Maps 3D (WebGL)
by feralchimp on Sunday January 08, 2012 @09:59PM
(#3441306)
That's all reasonable enough, but does it really excuse this UX?
1. User visits website with late-model hardware/OS.
2. Website says "this site requires browser foo."
3. User installs browser foo and reloads website.
4. Website says "error - check system configuration."
A technology demo with highly-specific client requirements, especially on the web, especially when the demo plays the look-mom-no-plugins card, should try to enumerate the actual requirements. In this case, the requirement that after installing latest Chrome, the fool at the keyboard navigate to chrome:flags and hit the big "turn WebGL on" toggle.
I understand why these types of doc omissions happen, but it's really a pretty serious bug. Every user that hits 1-4 above is a user who is actively dissuaded from caring about the technology that the rest of the site was designed (at non-trivial expense) to promote.
1. User visits website with late-model hardware/OS. 2. Website says "this site requires browser foo." 3. User installs browser foo and reloads website. 4. Website says "error - check system configuration."
A technology demo with highly-specific client requirements, especially on the web, especially when the demo plays the look-mom-no-plugins card, should try to enumerate the actual requirements. In this case, the requirement that after installing latest Chrome, the fool at the keyboard navigate to chrome:flags and hit the big "turn WebGL on" toggle.
I understand why these types of doc omissions happen, but it's really a pretty serious bug. Every user that hits 1-4 above is a user who is actively dissuaded from caring about the technology that the rest of the site was designed (at non-trivial expense) to promote.