In microsofts case it's the "metro" style, with lots of bright (almost cartoony) colors, big blocks filled with lots of light-weight, sans-serif fonts.
230 karma · joined November 1, 2011
http://trezoid.com || https://github.com/trezoid
In microsofts case it's the "metro" style, with lots of bright (almost cartoony) colors, big blocks filled with lots of light-weight, sans-serif fonts.
Apple has done this extremely well with the iTunes cards, which has made people more inclined to pay for apps.
Personally, I can't honestly see facebook being nearly as central in 5 years time, if it exists at all. Some hot new thing will come along and do sharing better and everyone will jump all at once.
Imagine if someone found your phone with email logged in. They would immediately be able to scan through your email for registration confirmation emails, go to that site and reset the password giving them complete access. If one of those accounts was for a site which saved cc details and had something the thief wanted (or could sell), they can drain your card with out setting off any fraud warnings, because you wanted to convenience of not having to type your password every time.
The problem is more that they don't compete well when the opposition are just text editors, and where people are perfectly happy to remove all the visual stuff.
I don't really see how something limited to a single OS/Browser combo is particularly useful by comparison.
Firstly, they're relying on javascript to do the striping effect, applying a class to even rows. If someone has javascript turned off this effect will degrade even in modern browsers.
Secondly, .stripes tbody tr:nth-of-type(2n){ background: #f6f6f6} achieves exactly the same thing in all modern browsers, and degrades just as well as the javascript version (even if javascript is off).
While I'm sure it could potentially be a problem in high-churn stores like gamestop, most places do have a replacement policy on discs that are scratched at purchase.
The development group is VERY active on IRC and there was some chatter at the time about that. Some of the slight lags in the demo were actually parts of the CSS transition they use (originally intended to avoid accidental swipes when they wanted taps) and was tweeked to be much better not long afterwards.
More recently there have been significant improvements in the actual CSS animation on the gecko side (improvements which will hit firefox in the future) which means everything feels even faster and more natural.
At this point B2G is making significant progress _every day_ so about the only real way to get an up to date idea of how it runs is to either read the github commit log frequently or put it on a device (and currently that means a GSII)
Further, apps will be able to request "trusted app" status to run with less cross domain restrictions.
Everything else works though.
It's all good in Chrome 16.0.912.63 on the above machine though.
also, it can't handle "gradient" at all.