Hacker News Reader

Comment by avenger123 | Hacker News Reader

This is for mobile HTML 5 development. If one was using the native implementation, there would be no need for this as you have pointed out.

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.

View on HN

I don't think Android Bootstrap has anything to do with HTML5. It's a set of themes for native Android apps duplicating the style of Twitter Bootstrap.

And it actually look very good. (https://dl.dropboxusercontent.com/u/5727009/screenshot-13841...)

I really can't differentiate between Disabled buttons and Rounded buttons. There would also be very little differentiation between the a basic button with no icon (because there isn't a good icon for everything) and the text input. Android design guidelines and 'language' is very different, and people expect the apps the buttosn to have some depth and clarity because of it. I, personally, would hate to have any of the apps that I use move to this style.

No it isn't. Read the README. It is a library for native Android apps to use.

Responsive frameworks like Bootstrap are already designed to work across desktops and mobile devices including Android, so there would be less of a motivation to make it specifically for Android. This is a native app boilerplate that creates the look and feel of Bootstrap.

> This is for mobile HTML 5 development.

This isn't for mobile HTML5 development.

Reply on news.ycombinator.com