This means that users will get a consistent user experience throughout various applications and won't have to run around trying to figure out what's a button and what's a text input.
Sadly, this project essentially destroys all of that work and something tells me it won't work correctly on the most customized devices (like the old Motorola RAZR running 2.3 for example).
Nice idea but I don't think it makes much sense in it's current state.
I suppose it makes sense from a branding perspective, but any designer worth their weight should be able to come up with a distinctive branded experience that doesn't revamp the entire, default, builtin experience on the device.
Unfortunate naming collision with Donn Felker's http://www.androidbootstrap.com/ though :(
Because the built-in resources are very Google-brand looking. Big apps have their own style. They'll follow UI norms, but don't need to look like Google made the app.
I guess the only real use is for the icon font, but people were doing that already and it's best practice to generate one with just the symbols you need.
This could be a good use case for sites that have a "mobile version" but don't want to/need to mimic the full android look but get close.
EDIT: I am definitely wrong on this (didn't read the docs careful enough). Thanks for the correction on this everyone.
This isn't for mobile HTML5 development.
