How Google should have done on-screen buttons (pic included)

6tr6tr

Well-known member
Dec 29, 2009
1,211
14
0
Visit site
It should have been off-screen by default and a screen-edge swipe brings it up when needed.
 

Attachments

  • buttonless1.jpg
    buttonless1.jpg
    17.4 KB · Views: 162

jgreeson25

Well-known member
Nov 20, 2012
106
0
0
Visit site
I like the idea, but I think it would get to be a bit testing to always have to swipe up to quickly go back a page/screen. When I first opened the box, I was surprised by the amount of bezel above and below the actual screen. Hopefully, in future iterations of the nexus line, this precious real-estate will be maximized and filled in with more screen space. Thereby, increasing the actual screen size while keeping the same or roughly the same form factor overall. I only mention this since it seems as though your concern is primarily based on wasted screen space due to the on screen buttons.
 

6tr6tr

Well-known member
Dec 29, 2009
1,211
14
0
Visit site
I like the idea, but I think it would get to be a bit testing to always have to swipe up to quickly go back a page/screen.

They could fix that by using the upside-down-backwards "L" swipe that blackberry has. So if you swipe up from the bottom and then continue swiping to the left (in one quick up-and-left swipe) it would simulate the back button.
 

DirkBelig

Well-known member
May 17, 2010
1,296
35
0
Visit site
Swiping up from the bottom is dedicated to bringing up Google Now.

What they should've done is either use the real estate under the screen for capacitive buttons - like the GS3, but w/o the stupid HW button - or halved the height of the on-screen buttons, making them the same height as the notification bar up top. We can hit that target (i.e. 24 px tall) easily, so there's no need to waste 48 px on the bottom. They can do the same double-height-on-touch action as the notification bar has, but just having that huge block at the bottom effectively makes our screens smaller than GS3 users' screens.
 

Dr0me

Well-known member
Jan 5, 2012
333
12
0
Visit site
Ubuntu comes to mind. I agree with them being under the screen like the GS3.

yes, ubuntu does it properly. You shouldnt need to swipe up, that just makes it harder to use the buttons. i dont mind that the on screen buttons take up space but would like to see the bezel smaller either way.
 

6tr6tr

Well-known member
Dec 29, 2009
1,211
14
0
Visit site
yes, ubuntu does it properly. You shouldnt need to swipe up, that just makes it harder to use the buttons. i dont mind that the on screen buttons take up space but would like to see the bezel smaller either way.

Ubuntu has a swipe up for the menu/action bar just like my example.

- - - Updated - - -

Swiping up from the bottom is dedicated to bringing up Google Now.

No, that's a swipe up from the home button, but they could always change that.
 

Nonymous666

Well-known member
Nov 16, 2012
213
0
16
Visit site
It should have been off-screen by default and a screen-edge swipe brings it up when needed.
I like the idea, but I think it should be configurable as to whether the buttons auto-hide or not. Personally, I wouldn't want to have to first swipe up every fricking time I want to hit the back button or switch to another running app.
 
Last edited:

6tr6tr

Well-known member
Dec 29, 2009
1,211
14
0
Visit site
I like the idea, but I think it should be configurable as to whether the buttons auto-hide or not. Personally, I wouldn't have to first swipe up every fricking time I want to hit the back button or switch to another running app.

They could do smart swipes like blackberry 10:

1. Swipe up and to the left = back button press
2. Swipe up and to the right = multitask button
 

josegb2011

Well-known member
May 2, 2012
99
0
0
Visit site
what i would do is make the home and back buttons moveable like the icons in the home screen and be able to customize it to your liking thus giving full screen support for anything..(apps,games etc)
 

XChrisX

Well-known member
Jun 24, 2012
768
18
0
Visit site
They could do smart swipes like blackberry 10:

1. Swipe up and to the left = back button press
2. Swipe up and to the right = multitask button

The only problem is those gestures aren't all that natural, and intuitive. It sounds nice on paper, but having to swipe up, and to the left or right just isn't a natural way of doing things on a smartphone.
 

6tr6tr

Well-known member
Dec 29, 2009
1,211
14
0
Visit site
The only problem is those gestures aren't all that natural, and intuitive. It sounds nice on paper, but having to swipe up, and to the left or right just isn't a natural way of doing things on a smartphone.

Neither was pinch-to-zoom when the first touchscreen smartphone arrived. (or two-finger swipe down in notification bar for Android 4.2) People learn these gestures very quickly.
 

FYourProblems

Well-known member
Nov 24, 2012
141
0
0
Visit site
IMO these buttons are too widely used for that. Next time you're on your phone pay attention to how much use the navigation bar gets, having to swipe to bring it up every single time would get old quick.
 

badbrad17

Well-known member
Dec 2, 2011
3,192
2
0
Visit site
I think it's just a matter of using the real estate that is available on the phone. If you look at the DNA compared to the Nexus 4 you can see there such a huge amount of space that's wasted. The DNA has literally the same amount of space plus all the space that the Nexus 4 uses for the buttons and even more space. There's no good reason why they designed it this way.

http://4.bp.blogspot.com/-xHdk0YTwJ...AADXw/Qb1JkPSySIQ/s1600/droid-dna-review7.jpg
Sent from my Nexus 4 using Android Central Forums
 

wunderbar

Well-known member
Dec 11, 2010
582
0
0
Visit site
Personally, I like the on screen buttons. They could have put less bezel on the bottom of the phone and made the screen a bit longer, but then that would have caused it to be a really odd screen resolution that would have given the developers yet another screen to design around (especially for video apps that hide the buttons).

Personally what I'd like to see more of is apps that do hide the buttons when displaying full screen content, like a lot of the video apps do, as opposed to just making the buttons the dim little dots. my two favorite examples of this are Google Play books and Pocket. When I'm reading full screen on either app I really the button bar would disappear entirely. if you tap the screen it brings up all sorts of controls for either app right now anyway. So why not do the same for the button bar at the bottom? Hide it most of the time but when you tap the screen to bring up the controls, bring up the buttons.

If more apps would do this it would alleviate a lot of the problems people do have with the buttons.
 

XChrisX

Well-known member
Jun 24, 2012
768
18
0
Visit site
Neither was pinch-to-zoom when the first touchscreen smartphone arrived. (or two-finger swipe down in notification bar for Android 4.2) People learn these gestures very quickly.

You can train your brain to learn anything if you truly want to, but it's just not as natural, and intuitive as pinch to zoom, and double tap to zoom as debuted on the original iPhone. I'm sorry, but I'm not a big fan of BB10, nothing all that fresh, and new here honestly.
 

KwietStorm

Well-known member
May 14, 2010
184
0
0
Visit site
I'm fine with it as it is, and I definitely do not want capacitive buttons. The bezel could be smaller, but that's something I've said about all phones, especially in the wake of the huge screen love fest.
 

palitsyn

Well-known member
Jul 25, 2012
74
0
0
Visit site
IMO these buttons are too widely used for that. Next time you're on your phone pay attention to how much use the navigation bar gets, having to swipe to bring it up every single time would get old quick.

I totally agree. I would hate if if I had to swipe up to get to the basic controls I probably use the most on the phone.