Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Android Bootstrap

github.com

Post reply on HN
Print view View original

21–25 of 25 posts

Re: Android Bootstrap

#21

Post by CervezaPorFavor »

radley wrote: post #16
aferreira wrote: post #13

One thing that I like about Android is that developers can choose to minimally style buttons and similar UI elements and these differences will be applied to whatever the base device theme is. 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…

Following UX/UI patterns make sense, but not design - especially if you plan to be cross platform.

I hate it when apps don't feel 'native' for the sake of cross-platform consistency. It's stupid.

Re: Android Bootstrap

#22

Post by mayanksinghal »

dragos2 wrote: post #6
ctz wrote: post #4

Earlier quoted context omitted.

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.

Re: Android Bootstrap

#23

Post by aferreira »

thwarted wrote: post #20
radley wrote: post #16

Earlier quoted context omitted.

Following UX/UI patterns make sense, but not design - especially if you plan to be cross platform.

What's the logic here? If you're cross platform, most people are most likely not going to be using your app on more than one platform, so there's little to be gained from a "consistent experience across platforms" angle. It's rare that the same person or team is doing both iOS and Android development, and the languages and layout methods are different anyway, so there's little to be gained on the development side in…

I can see where he's coming from, my company is actually at fault on this exact point.

The initial target was iOS and then clients requested Android compatibility as well. Designs for iOS are completed and implemented and are then re-used for Android. The excuse is 'consistent user experience' but really they just don't want to do the same job twice for a platform that generally has less usage and provides less profit (in our case at least).

I took matters into my own hands and there are noticeable differences between the two applications. There was of course some backlash (I flat out refused to put a 'back' button on the action bar for example or move the sliding menu to the right side) but in general the look and feel is consistent across the two platforms.

That doesn't (and won't) stop me from using native controls such as text inputs and dialogs that users on Android are quite familiar with.

In case someone has no clue what the hell I'm talking about I'd be happy to share some screenshots via pm.

Re: Android Bootstrap

#24

Post by thwarted »

aferreira wrote: post #23
thwarted wrote: post #20

Earlier quoted context omitted.

What's the logic here? If you're cross platform, most people are most likely not going to be using your app on more than one platform, so there's little to be gained from a "consistent experience across platforms" angle. It's rare that the same person or team is doing both iOS and Android development, and the languages and layout methods are different anyway, so there's little to be gained on the development side in…

I can see where he's coming from, my company is actually at fault on this exact point. The initial target was iOS and then clients requested Android compatibility as well. Designs for iOS are completed and implemented and are then re-used for Android. The excuse is 'consistent user experience' but really they just don't want to do the same job twice for a platform that generally has less usage and provides less profi…

Designs for iOS are completed and implemented and are then re-used for Android. The excuse is 'consistent user experience' but really they just don't want to do the same job twice

Yeah, this is a sign of a bad PM, who doesn't understand the market or mobile ecosystem enough to realize that the targets are completely different.

On the other hand, if the interface was designed to be completely unique and skirted all the specifics of the deployment platform, in an attempt to be branded or for reuse of designs, that's reasonable. Often, however, it is obvious that the design was optimized for another platform than the one you're using it on. "Custom back button" on Android, indeed.

Re: Android Bootstrap

#25

Post by dragos2 »

thwarted wrote: post #24
aferreira wrote: post #23

Earlier quoted context omitted.

I can see where he's coming from, my company is actually at fault on this exact point. The initial target was iOS and then clients requested Android compatibility as well. Designs for iOS are completed and implemented and are then re-used for Android. The excuse is 'consistent user experience' but really they just don't want to do the same job twice for a platform that generally has less usage and provides less profi…

Designs for iOS are completed and implemented and are then re-used for Android. The excuse is 'consistent user experience' but really they just don't want to do the same job twice Yeah, this is a sign of a bad PM, who doesn't understand the market or mobile ecosystem enough to realize that the targets are completely different. On the other hand, if the interface was designed to be completely unique and skirted all th…

I too am faced with the "custom back button" on Android. I just smile and carry on.
Post reply on HN