Results 1 to 22 of 22
Like Tree10Likes
  • 1 Post By 6tr6tr
  • 1 Post By DirkBelig
  • 2 Post By XChrisX
  • 5 Post By FYourProblems
  • 1 Post By palitsyn
  1. Thread Author  Thread Author    #1  

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

    It should have been off-screen by default and a screen-edge swipe brings it up when needed.
    Attached Thumbnails Attached Thumbnails How Google should have done on-screen buttons (pic included)-buttonless1.jpg  
    tommyjoesanders likes this.
  2. #2  

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

    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.
  3. Thread Author  Thread Author    #3  

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

    Quote Originally Posted by jgreeson25 View Post
    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.
  4. #4  

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

    That means that the OS would be gesture based like the new BB10 and Playbook software.
    Teenage app developer for Auto Forum. Be sure to download Auto Forum from Google Play!
  5. #5  

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

    Or like WebOS, may it rest in piece

    Run, do NOT walk, and get a Nexus 7. You can thank me later.
    Palm IIIxe, Handspring Prism, Sony CLie, Tapwave Zodiac, Centro(AT&T), Palm Pre Plus(AT&T), Nook Color, HP Touchpad-32, HP Veer, Samsung Galaxy Note(AT&T), Nexus 7 (32), Nexus 4 (16)
  6. #6  
    DirkBelig's Avatar

    Posts
    1,267 Posts
    Global Posts
    1,412 Global Posts
    ROM
    Stock

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

    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.
    "The Nexus 5 is such a big black slab of power that if you dropped it down in the middle of a pack of monkeys, they'd start using weapons." - Dirk Belligerent.
    Devices: 32GB Nexus 5, 16GB Nexus 7 (2013), 16GB Nexus 7, 16GB Nexus 4, ASUS Transformer TF101, Kindle Fire, HP TouchPad (CM7), Samsung Galaxy S II Epic 4G Touch Long Name Phone, HTC EVO 4G, Palm Pre, 64GB 1st gen iPad WiFi
    AbuYazeedUK likes this.
  7. #7  

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

    Ubuntu comes to mind. I agree with them being under the screen like the GS3.
  8. #8  
    Dr0me's Avatar

    Posts
    333 Posts
    Global Posts
    334 Global Posts
    ROM
    AOKP PUB / Franco Kernel

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

    Quote Originally Posted by AbuYazeedUK View Post
    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.
    Google Android Affectionado
  9. Thread Author  Thread Author    #9  

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

    Quote Originally Posted by Dr0me View Post
    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 - - -

    Quote Originally Posted by DirkBelig View Post
    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.
  10. #10  

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

    Quote Originally Posted by 6tr6tr View Post
    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 by Nonymous666; 01-16-2013 at 04:12 PM.
  11. Thread Author  Thread Author    #11  

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

    Quote Originally Posted by Nonymous666 View Post
    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
  12. #12  

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

    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)
  13. #13  

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

    Quote Originally Posted by 6tr6tr View Post
    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.
    Living large with my Galaxy Note 3!!!
    KwietStorm and Ry like this.
  14. Thread Author  Thread Author    #14  

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

    Quote Originally Posted by ChrisXe View Post
    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.
  15. #15  

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

    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.
    Thanked by 2:
    KwietStorm, Ry, zedorda and 2 others like this.
  16. #16  
    badbrad17's Avatar

    Posts
    3,284 Posts
    ROM
    Stock JB 4.4 Rooted

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

    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.


    Sent from my Nexus 4 using Android Central Forums
    Android Evangelist
    HTC Desire + Samsung Galaxy SIIx + Transformer TF101 and Prime + Nexus 4
  17. #17  

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

    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.
  18. #18  

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

    Quote Originally Posted by 6tr6tr View Post
    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.
    Living large with my Galaxy Note 3!!!
  19. #19  

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

    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.
  20. #20  

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

    Quote Originally Posted by FYourProblems View Post
    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.
    HTC One 32GB (silver), Nexus 4 16GB, iPhone 4s 16GB, Nexus 7 16GB
    FYourProblems likes this.
  21. #21  

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

    your wish is AOKP's command

  22. #22  
    Ry
    Ry is online now
    Ry's Avatar

    Posts
    7,190 Posts
    Global Posts
    7,197 Global Posts

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

    I'd rather keep it the way it is.
    a.k.a. RyZR from HoFo
    Motorola Moto X (164.55.2.ghost_verizon.Verizon.en.US, KitKat 4.4.2)
    Motorola Moto G (173.44.20.falcon_cdma.Verizon.en.US, KitKat 4.4.2)
    Motorola DROID Bionic (98.72.22.XT865.Verizon.en.US, Jelly Bean 4.1.2)
    Google Nexus 7 2012 (KOT49H, KitKat 4.4.2)
    What other devices have I had? Here's my phone timeline.
    Support your favorite Android app and game developers. Pay for apps! And don't block ads!

    Community Rules & Guidelines - Mobile Nations Forums

Similar Threads

  1. How to flash "on screen buttons" to Nexus S
    By Primed4nexus in forum AT&T Nexus S Rooting, ROMs, and Hacks
    Replies: 1
    Last Post: 01-25-2012, 11:53 PM
  2. This is how ICS should have done the buttonless screen!
    By 6tr6tr in forum Google / Samsung Galaxy Nexus
    Replies: 7
    Last Post: 10-20-2011, 12:32 AM
  3. Soft/On Screen Buttons Potential Problems
    By jmart603 in forum Verizon Galaxy Nexus
    Replies: 59
    Last Post: 10-11-2011, 04:54 PM
  4. Should have done this a while ago...
    By mobilern11 in forum Introductions
    Replies: 1
    Last Post: 09-08-2011, 10:55 PM
  5. How I would have done the Nexus S
    By 6tr6tr in forum Sprint Nexus S 4G
    Replies: 3
    Last Post: 08-04-2011, 08:11 PM

Posting Permissions

B