Slashdot Mirror


Android Q May Change the Back Button To a Gesture (theverge.com)

Android's back button might be going away entirely, replaced with a quick swipe to the left from the home button. From a report: XDA Developers has been digging into a leaked, early set of code from the next version of Android, codenamed Q, and the latest discovery from those forays is this potential demise of the back button, as well as a quicker app-changing animation when you swipe to the right. The way that gestures and buttons work in Android 9 Pie (the current iteration, at least if you're lucky enough to own a phone that runs it) is a little bit split. Google's Pixel has just a home "pill" and then a back button appears only when it's needed.

Here's a quick video XDA made showing the gesture system Google is experimenting with in Android Q. It is, as anybody could have predicted, a little messy. For something as core to a phone as "going home" or "going back," the fact that different phones have different methods could be a problem.

130 comments

  1. Physical buttons by Anonymous Coward · · Score: 3, Insightful

    I'm glad my device has physical buttons. Hopeful!y there is a way to disable this on other devices.

    1. Re: Physical buttons by Anonymous Coward · · Score: 2, Insightful

      Google developers cannot read so they have no idea there were home and back buttons and they invented a gesture. No thanks

    2. Re: Physical buttons by Marxist+Hacker+42 · · Score: 1

      Will somebody please make a phone with a physical keyboard again?!?!?!? I miss my physical keyboards.

      Gestures are non-inclusive.

      --
      SJW: a person who perceives an injustice, and while correcting it, commits a greater injustice.
    3. Re: Physical buttons by fbobraga · · Score: 1

      I liked physical keyboards at first too, but now I'm used to swipe to type, and realized it is faster... (and the lighter and thinner devices without an physical keyboard had me :P)

    4. Re: Physical buttons by Anonymous Coward · · Score: 0

      My Galaxy S Relay recently died and I am still in mourning. I *loved* that qwerty keyboard and am pissed that the insurance I had on it will only get me a "similar" replacement, which is not similar at all (Galaxy 5S) and has no keyboard. I am tempted to find an unlocked one, but they are all so old now that I suspect finding a working one with a battery that still has a decent life will be more trouble than its worth.

    5. Re:Physical buttons by Anonymous Coward · · Score: 0

      I'm glad my device has physical buttons. Hopeful!y there is a way to disable this on other devices.

      Agreed. There are perfectly good small legacy apps even from Google (looking at you, AOSP Music!) whose APKs would be pretty fast, slim and cool carried over to newer devices.

      Except for the confusion and eventual surprise realization that they were rendered quite useless on your new device. At some point Google designed a separation between a menu triggered by a longpress and one triggered via the once-mandatory physical button on every Android device. Android 4 was pretty insensitive in deprecating the option when it refused to engineer an alternative. And such a life-saver was the more rude as we know that despite that version's introduction of the silly dynamic non-hardware button overlay (which some phones autohide, to make people even more confused) no customization a-la Notification-shade widgets or Firefox browser toolbar was allowed for those of us who needed it.

      The fad of deprecation without proper replacements being left behind is the whole reason why people shouldn't trust any upgrades. You're just being slowly painted into a corner.
      Given the prior track record of Google's intentional crippling of Chrome's address bar, and their perchant for Analytics, I wouldn't be surprised to hear that they make intentional regressions just to measure how the lab rats deal with frustration, confusion and anger (like Facebook has been known to secretly do in staged tests)

    6. Re: Physical buttons by arglebargle_xiv · · Score: 1

      Gestures are non-inclusive.

      Well, I dunno, I think this gesture pretty much sums up everything I need to say about Google's constant fscking with the Android UI.

    7. Re: Physical buttons by Anonymous Coward · · Score: 0

      Blackberry still sells their slide out keyboard android phone, I can't say it's good because I never used it but I've considered getting one

    8. Re:Physical buttons by Anonymous Coward · · Score: 0

      I'm glad my device has physical buttons. Hopeful!y there is a way to disable this on other devices.

      No no no..... Google wants you to be forced to make obscene gestures instead!

    9. Re: Physical buttons by Anonymous Coward · · Score: 0

      Will somebody please make a phone with a physical keyboard again?!?!?!? I miss my physical keyboards.

      Gestures are non-inclusive.

      Android powered BlackBerry phones like Priv, Key One and Key Two are modern phones with physical keyboards

      Planet Computers also makes the Gemini and the Cosmo Communicator, both are android phones with physical keyboards
      (Planet Computers devices CAN run a real linux and sailfish also though, even in a dual or triple boot setup)

  2. Force quit by ichthus · · Score: 3, Insightful

    This is fine, but I hope they somehow retain long-hold-on-back-button = force quit (enabled in developer options). I love this feature.

    --
    sig: sauer
    1. Re: Force quit by Anonymous Coward · · Score: 0

      Force quit. So rarely required in iOS. Thank you so much for this.

    2. Re: Force quit by bhcompy · · Score: 2

      The things I force quit in Android are things that run in the background that I want to stop running. iOS is much more restrictive about what runs in the background, so I don't have the problem of having to force quit those applications on iOS, but that also means I'm installing those applications on Android because they work better. So, yea, I quit less on iOS, but I also do less because of it's limitations(disclosure: I carry two phones, one iOS based and one Android based).

      That said, Android has started to shift in the iOS direction with Pie in regards to restricting background processes, and will seemingly double down on that route with Q, and it's put a lot of useful applications that run in the background in a bad spot as they've become more unreliable without excluding them from Pie's aggressive battery optimizations and background services restrictions(through banner requirements, which don't really alleviate the issue in my experience).

    3. Re: Force quit by Anonymous Coward · · Score: 0

      When iOS panics it just aborts the program. Crashes to the home screen.

      Or it's supposed to. I'm pretty sure I remember having to hard power my work ipad, when I still bothered using it. Kinda-sure.

      Sometimes it felt RAM related, as if buildup crossed an illegal threshold and so the whole plug is yanked. Similar Android behavior. I just chalk it up to "LOL MOBILE."

    4. Re: Force quit by ichthus · · Score: 1

      Thank you so much for this.

      I'm glad I could brighten your life. Hopefully, you can find other things to bring joy to your day, like the car you drive, or not owning a TV, or something.

      --
      sig: sauer
    5. Re:Force quit by mjwx · · Score: 1

      This is fine, but I hope they somehow retain long-hold-on-back-button = force quit (enabled in developer options). I love this feature.

      They'll keep it. This is just the Google Hype/Hate cycle warming up.

      1. Google announces that they're developing a new feature in $product.
      2. The "tech" media ignore the actual press release and use Buzzfeedian headlines like "OMG WAFFLEBOTTOM GOOGLE WILL TAEK ALL YOUR THINGS".
      3. The Twiterarti start twatling "Holy TESTICLEBALLS I am Angry at Google doing a thing I'm not even sure what they're doing but I"M AGRNY. Even though I"M a shameless APPLE FANBOY (bless his Steveness) IM selling ALL MY ANDROID THINGS I DONT HAVE".
      4. Repeat steps 2 and 3 ad nauseam.
      5. New feature is either released side by side or quietly dropped if it doesn't work.

      They might be working on gesture based things but they're usually never work as well as intended and Google are smart enough to realise this.

      --
      Calling someone a "hater" only means you can not rationally rebut their argument.
  3. Buttons by fluffernutter · · Score: 5, Insightful

    How is a swipe easier than a button? Why can't people understand buttons??

    --
    Laws are rules for the court, but merely a bottom bar to hit for life. Think beyond laws in your actions always.
    1. Re:Buttons by Anonymous Coward · · Score: 4, Interesting

      It's not easier, they just want more minor annoyances to detract from larger grievances

    2. Re:Buttons by Anonymous Coward · · Score: 1

      Because gestures!

    3. Re:Buttons by Fly+Swatter · · Score: 2

      From marketing dept: Buttons just get in the way of our zero bezel goal, anything else will sell less phones - trust us.

    4. Re:Buttons by DontBeAMoran · · Score: 2

      A swipe is easier because it uses the touch display that's already needed. It doesn't cost anything, it doesn't take any room, it can't break unless the display itself breaks.

      A physical button adds complexity, adds cost, adds manufacturing time, adds a potential failure point and takes a lot more room than a swipe gesture (which takes no room at all).

      --
      #DeleteFacebook
    5. Re:Buttons by DarkRookie2 · · Score: 2

      takes a lot more room than a swipe gesture (which takes no room at all)

      This is wrong. I need my whole screen to make a gesture. The software button is a lot smaller than that.

      --
      http://progressquest.com/spoltog.php?name=Son+Of+Son+Of+DarkRookie
    6. Re:Buttons by Anonymous Coward · · Score: 1

      I had an HP Pre3, the last iteration of WebOS on a phone. It had no buttons, just a gesture zone in the bottom. Nothing I have seen since ever came close to the versatility of the controls available through a "Gesture zone". (It combined more than 5 button functions)

      Indeed, it was completely undiscoverable, I had to watch a tutorial video to learn to use the phone. But the gestures have stuck with me.
      The main issue I have with buttons in the bottom of a smart phone is how easy it is to miss the button, and hit one of the two others, or none. Yes, I have long fingers.

    7. Re:Buttons by Anonymous Coward · · Score: 1

      It also potentially interferes with apps you may be running. Either the gesture is going to have to be overly complex as to be cumbersome, or it's likely to interfere with many games such as fruit ninja.

    8. Re:Buttons by AuMatar · · Score: 2

      That's great- except they went to virtual buttons a long time ago. THere's no advantage in a swipe over an onscreen virtual button.

      --
      I still have more fans than freaks. WTF is wrong with you people?
    9. Re:Buttons by Anonymous Coward · · Score: 0

      Physical buttons are probably going away, but virtual buttons have most of those same advantages, unless one has a notch fetish. The swipe probably needs to start on the home "pill" in order to differentiate it from a swipe inside the app.

    10. Re:Buttons by Anonymous Coward · · Score: 0

      I hate swipe UIs, especially on phones, you're basically requiring that I hold it delicately by the edges and use my other hand to run it at that point. Bad!

    11. Re:Buttons by AmiMoJo · · Score: 1

      My guess is it's an experiment to see if they can get rid of the on-screen buttons entirely. It will doubtless be an option, just like you can change the order of the current buttons or disable them on phones with hardware ones.

      Like say you are watching a full screen video, at the moment you have to tap once to bring up the buttons and then again on the button. With a gesture you could just swipe where the button would be, similar to how iOS handles the home/switch gesture.

      --
      const int one = 65536; (Silvermoon, Texture.cs)
      SJW, n: "Someone I don't like, and by the way I'm a fuckwit" - AC
    12. Re:Buttons by Dutch+Gun · · Score: 1

      I'd guess the answer is "screen space". There's an argument to be made that this could increase space for apps.

      I'm not really sure I buy that argument, as I use a phone with two physical buttons, and am used to that. Would have to use it for a while, I guess.

      --
      Irony: Agile development has too much intertia to be abandoned now.
    13. Re:Buttons by DarkRookie2 · · Score: 2

      They can shove the screen space argument up their collective asses until the remove a lot of the extra padding, margins, and whitespace from their apps first.

      --
      http://progressquest.com/spoltog.php?name=Son+Of+Son+Of+DarkRookie
    14. Re:Buttons by Dixie_Flatline · · Score: 1

      You don't really, just a small space at the bottom of the screen. I wouldn't say that it takes less space, but it probably takes no more real space.

      The advantage to gestures is that they're a lot easier to use on the huge phones that have been foisted on us, regardless of hand size. There's no reaching for anything if you're holding your phone from the bottom already.

      The (significant) disadvantage is that they're an extra thing to learn, and they're not discoverable. There is very little about the bar across the bottom of my iPhone XR that indicates what will happen if I interact with it. At best, I can take it as a marker that some sort of interaction is available, but that's it. If I don't know how to use it and I make a mistake, I might discover the other functionality.

      I LIKE the gestures on my iPhone. I like them better than the home button, I'd say. But from a UI perspective, I have major reservations about how these features are communicated and made obvious. Frankly, in that sense, they're a nightmare, and nobody has solved that issue yet that I've seen.

    15. Re:Buttons by swillden · · Score: 1

      They can shove the screen space argument up their collective asses until the remove a lot of the extra padding, margins, and whitespace from their apps first.

      Who is "they"?

      You know the people who build the operating system UI aren't the same people who write apps, right?

      --
      Note to ACs: I usually delete AC replies without reading them. If you want to talk to me, log in.
    16. Re:Buttons by fluffernutter · · Score: 1

      I have very big hands, but that's why I get a big phone. I don't know if the Note 9 is the biggest but it seems to fit my hand and I can use the stylus too for finer work.

      --
      Laws are rules for the court, but merely a bottom bar to hit for life. Think beyond laws in your actions always.
    17. Re:Buttons by fluffernutter · · Score: 1

      Apple and Samsung

      --
      Laws are rules for the court, but merely a bottom bar to hit for life. Think beyond laws in your actions always.
    18. Re:Buttons by fluffernutter · · Score: 2

      I'm fine with virtual buttons. I just don't like gestures. My hands are too big to do things like that constantly on a phone.

      --
      Laws are rules for the court, but merely a bottom bar to hit for life. Think beyond laws in your actions always.
    19. Re:Buttons by Dixie_Flatline · · Score: 1

      A lot of that extra padding and whitespace is useful guidance in its own right, from a UI perspective. It makes things easier to read and delineate and manipulate. We're working on fundamentally space-limited devices, so crowding the UI doesn't make any more sense.

      But you're right that it's still not a good argument. I *know* the screen space is limited. I'm coming into my phone experience expecting something different from my PC. I think they make large devices easier to use with one hand if you already know exactly what you're doing, but they're terrible if you don't. Phones are already becoming something of a "hard-mode" device from a discoverability perspective, and this is just exacerbating it.

    20. Re:Buttons by Archangel+Michael · · Score: 1

      A swipe isn't easier. Is the swipe right to left, left to right? Does it flip depending on RTL languages or not? Which direction is back again?

      --
      Agent K: A *person* is smart. People are dumb, stupid, panicky animals, and you know it.
    21. Re:Buttons by DarkRookie2 · · Score: 1

      The OS makers and the devs that follow them.

      --
      http://progressquest.com/spoltog.php?name=Son+Of+Son+Of+DarkRookie
    22. Re:Buttons by mobby_6kl · · Score: 1

      I don't think that's correct. You can prefer the virtual buttons of course but there are some pros and cons for the gestures too. I actually use a Windows 10 tablet so I might be the only one in this discussion who has actual experience with gestures.

      A swipe from the left opens the task switcher thing, and a swipe from the right opens the notification/option panel (much like the androd drawer). Swiping from the top lets you tile multiple windows automatically. Bottom is for showing the navigation bar (the one with win/back buttons) if it's hidden.

      I don't use the device that often but I still miss it on my Note9 sometimes (though it seems like the latest update introduced the back/forward swipe from left/right) gestures.

      Pros for gestures:
      * Don't take up screen space
      * Can work in fullscreen apps
      * Work along the entire screen/edge (this can be very significant depending on the size of the device and how you hold it)

      Cons
      *Less discoverable (but takes like a minute to learn)
      *???

      Maybe there's some other downside I'm missing but I honestly don't see it based on my experience with Win10, so at the very least I'd be happy to try a gesture-based Android.

    23. Re:Buttons by hey! · · Score: 3, Interesting

      A lot of phone UI changes are not about making phones easier to *use*, they're about making the phones easier to *sell*.

      Consider wrap around screens -- do they actually *improve* the functionality of the phone in any way? Or do they exist just to make you say "ooh" the first time you hold it? Or ultra-thin phones -- is a 7mm phone any more convenient, or would you rather have a 10mm phone with 2x the battery?

      The very earliest Android phones had a dedicated area with four buttons stenciled on it: back, menu, home, and search. Now there's other reasons they did it this way, but this happens to be the way a UI functionality purist would design the interface. The button row interface is (1) manifest (you see there's a widget there to frob and it gives you some hint of what it's about), and (2) stable (those common buttons are always in the exact same place).

      Every change made accessing these functions since that day hasn't been to make the users' lives easier; it's been to impress them when they're shopping for phones. And it quite evidently works, so you can't really blame Google or the phone manufacturers. Consumers get excited by novelty. You'll never get better vendors until you get better consumers.

      --
      Post may contain irony: discontinue use if experiencing mood swings, nausea or elevated blood pressure.
    24. Re:Buttons by AuMatar · · Score: 3, Insightful

      No, there aren't any pros for gestures. They're less discoverable, require more effort, and they don't work in fullscreen apps like you claim- they are in fact far more likely to interfere in apps at any size because swiping is a very common operation. This is just a horrible idea from start to finish.

      --
      I still have more fans than freaks. WTF is wrong with you people?
    25. Re:Buttons by Solandri · · Score: 1

      Motorola already has this option. You can use the fingerprint sensor to replace the back / home / running apps / power buttons. Back becomes a left swipe, home becomes a short tap, running apps becomes a right swipe, and power becomes a long tap.

      It takes a little getting used to, and I still perform the wrong action maybe 1 in 20 times (mostly a problem with short and long and extremely long tap not being different enough - the last one activates Google Assistant which I never use; wish I could adjust the activation durations). But it turns out to be more convenient because (1) the Android buttons are now pop-up overlays which disappear to give the running app the entire screen, and require a tap or swipe up to make them reappear, and (2) you don't have to move your finger around to reach for the different button locations. So all four functions always available with no extra gestures needed, and are all four are always in the same location so you don't have to visually spot them to move your finger to the correct one.

      However, not everyone likes this. And I think the most important thing is that Motorola gives you the option to pick whichever method you like - the original style buttons, or using gestures. Historically, Google has had this bad Apple-like habit of forcing you to adopt their newfangled system even if you prefer the old way.

    26. Re:Buttons by DontBeAMoran · · Score: 1

      I call that "functionality through obscurity".

      --
      #DeleteFacebook
    27. Re:Buttons by DontBeAMoran · · Score: 1

      Is the swipe right to left, left to right?

      Yes.

      --
      #DeleteFacebook
    28. Re:Buttons by fluffernutter · · Score: 1

      I don't like anything that can do random things when I put my phone in my pocket without locking it.

      --
      Laws are rules for the court, but merely a bottom bar to hit for life. Think beyond laws in your actions always.
    29. Re:Buttons by mobby_6kl · · Score: 1

      Really, less wasted screen space isn't a pro, even a minor one that you don't prioritize? And I already mentioned they're less discoverable as the downside. But it takes 10 seconds to explain and then it's trivial to remember forever, so it's a minor one.

      How do gestures require more effort? In fact I'd say they require less effort, you just make a small swiping motion right where you're holding the device instead of having to move the hand/finger to the bottom where the buttons are (sometimes, unless you're in a fullscreen app and then they're hidden).

      And gestures absolutely do work with fullscreen apps exactly as I say they do. I know this because I just tried it. In Android, in some NFS game: swiping from top opens the drawer, swiping from the right shows the navigation menu. It never ever gets in the way because you don't swipe like that during normal use. On Win10, in KSP: does exactly what I said before, although also minimizes the window but that has more to do with the window mode than anything else.

    30. Re:Buttons by narcc · · Score: 1

      I couldn't agree more. WebOS had a brilliant UI. BB10 as well. It only takes a couple of minutes to learn the gestures, then they're second nature. I still find myself trying BB10 gestures on Android phones.

      Both of those UIs were years ahead of the competition. It's a real shame we haven't seen iOS or Android "steal" them.

    31. Re:Buttons by Anonymous Coward · · Score: 0

      Wrong. You can replace the tactile button with a touchscreen button. Gives you that zero bezel , all screen experience. Of course, most of the time the button is displayed there, but it can go away (or go semi-transparent) when viewing images/video. But most of the time, the button should be there.

      Of course, some will still miss their "real button". But a touch button is a small change that achieve that zero bezel. Changing to a swipe is bad. Apps already uses swipes their own way. And it is different for no good reason.

      I already fail to teach old people to use buttonless smartphones. They don't "get" how the screen interface changes all the time. Replacing buttons with swipes makes it harder for more than the old. They young will surely adjust - but there don't seem to be any benefit for them either.

      Change for change's sake. The sickness that happens when they fail to renew the hardware. Quit this nonsense - develop those westworld-style phones that fold twice. That'd be something worth buying!

    32. Re:Buttons by Anonymous Coward · · Score: 1

      Everytime you hand the phone to someone, the app exits. Showing stuff becomes harder.

    33. Re:Buttons by Anonymous Coward · · Score: 0

      I have to use the screenlock feature because the singlebutton (ie hockey puck) UI of touch-only operation is already shitty.

      More "interpretation" while I'm watching video isn't an upgrade.

    34. Re:Buttons by Zaelath · · Score: 1

      How do gestures require more effort?

      Oooh, that's an easy one.

      On the Nokia 8 the home button is the fingerprint scan button, like an iPhone I guess.

      When the banking app asks you to verify your thumb print, half the time it works, half the time it goes to the home screen. Maybe more than half, so then it's a few guestures/presses to get back to the banking app, and try and work out if it wants a short, medium, or long press, and is the pressure the issue or is it just the length of contact? Nope, wrong guess, go around again, etc, ad nauseum.

      Overloading things is "cool" and "clean" but it's not easier.

    35. Re:Buttons by PCM2 · · Score: 1

      I'm not a huge fan of behaviors that are not discoverable, i.e. the only way you can activate it is if you know the secret trick, like a swipe. I've watched my mom do stuff like press harder on her phone screen because she doesn't realize that she has to use her actual fingertips and not her fake fingernails. I doubt she would ever figure out gestures, and I barely use them myself. Even I discover Android features that are activated by gestures that I never knew about.

      --
      Breakfast served all day!
    36. Re:Buttons by aybiss · · Score: 1

      But you're not saving any screenspace. All you're doing is not drawing *one* of buttons that come up when you swipe from the edge of the screen.

      --
      It's OK Bender, there's no such thing as 2.
  4. I've seen no difference between by Anonymous Coward · · Score: 0

    the last three versions, so I'm not exactly sure why there is a new android every other week. Stop it, fix the bugs, let me take it easy.

    1. Re:I've seen no difference between by Anonymous Coward · · Score: 0

      It's nothing close to "every other week".

      There are monthly security updates, but major versions happen once a year.

  5. Fuck gestures by DarkRookie2 · · Score: 5, Insightful

    Gestures have to be the most opaque way to interact with anything.

    --
    http://progressquest.com/spoltog.php?name=Son+Of+Son+Of+DarkRookie
    1. Re:Fuck gestures by Anonymous Coward · · Score: 1

      Especially "to the left" which always implies 'forward' to me... same way you typically flip the page of a book/magazine 'to the left' to go forward.

      'Home' always implies 'back to the beginning'..ie keep hitting the back button on the browser and eventually get to the home page.

      So why not have a gesture which implies the exact opposite of what it does...Brilliant!

    2. Re:Fuck gestures by GuB-42 · · Score: 4, Insightful

      I found the "fuck gesture" to be a very clear way of interacting with people.
      For example, if you meet some UI designers from Google, it can be used to show how much you appreciate their work.

    3. Re:Fuck gestures by Anonymous Coward · · Score: 0

      This! Exactly this!

      Google: If you're listening - I don't want an iPhone. I want exactly the opposite of an iPhone.

  6. Change for the sake of change by Anonymous Coward · · Score: 0

    The progressive thought process.

  7. Stop Screwing with the Interface... by sqorbit · · Score: 4, Insightful

    If it' ain't broke, don't fix it. Seriously though, why do developers (yes I'm talking to you too GNOME) feel the need to constantly change UI's? If something is working and working well for the users why change for the sake of having something "new". It's purely to add things to a feature list. People - If it ain't broke don't fix it. Engineers - If it' ain't broke we haven't added enough features.

    --
    Sent from my TARDIS
    1. Re:Stop Screwing with the Interface... by Anonymous Coward · · Score: 0

      To leave people who like consistent behavior in the dust. They want you to spend as much time acclimating yourself as you do actual using the device.

      My parents love shit like this. /s

    2. Re:Stop Screwing with the Interface... by Anonymous Coward · · Score: 2, Insightful

      If the studies were right they wouldn't have to change anything, yet here we are. Sounds like the studies keep drawing different conclusions.

      I'm glad I don't have to keep re-learning how to open my fridge or running the faucet or using a bar of soap.

    3. Re:Stop Screwing with the Interface... by Paul+Neubauer · · Score: 1

      There is much truth in this. One, if not The, lesson of working one place was Thou Shalt Not [Monkey] With The User Interface. Even if it seems sub-optimal, it's what is expected and changing it will result in ill-will at best. Any UI change must be thought over very carefully, and change made only if it is a HUGE win - as seen by the user.

      --
      I don't subscribe to RMS's GNUtopian vision.
    4. Re: Stop Screwing with the Interface... by Anonymous Coward · · Score: 0

      Sounds like the studies are being conducted by qwacks

    5. Re:Stop Screwing with the Interface... by GuB-42 · · Score: 1

      Because people don't realize something changed unless the appearance changed.
      I think I've read that in an interview of someone from Microsoft. He gave the Windows calculator as an example: when they started using rational numbers internally in order to avoid rounding errors, no one noticed, because the UI stayed the same.
      I have a personal example of the opposite. We maintain an issue at work (a modified version of Mantis). Our last update was a massive improvement according to users. In fact, the only thing that changed significantly was the style, by that I mean colors and shapes, nothing functional.

    6. Re:Stop Screwing with the Interface... by Anonymous Coward · · Score: 0

      I think each new group of developers think they know better than the previous group of developers. Or if it's the same group of developers, then they feel they need to keep changing things to keep working (aka keep their job).

      In general I think those two scenarios, keeps the tech industry reinventing the wheel over and over and over.

      Operating Systems and UIs should be commodity parts by now. I'm not saying you they can't get better, but most changes are for the sake of changes, instead of real improvements.

    7. Re: Stop Screwing with the Interface... by Anonymous Coward · · Score: 0

      They're being conducted by people who keep wanting to get paid to do more studies. "We're tracking all kinds of new trends that could impact everything in a new way! Productivity and discoverability and synergy and other buzzwords will skyrocket! Honest!"

    8. Re:Stop Screwing with the Interface... by Anonymous Coward · · Score: 0

      No, this is to make way for facial recognition. First, change it to a gesture; second, change the gesture to the "face detected and looking at me" gesture. This is not for you. It is for your masters.

    9. Re:Stop Screwing with the Interface... by Anonymous Coward · · Score: 0

      If it' ain't broke, don't fix it. Seriously though, why do developers (yes I'm talking to you too GNOME) feel the need to constantly change UI's? If something is working and working well for the users why change for the sake of having something "new". It's purely to add things to a feature list. People - If it ain't broke don't fix it. Engineers - If it' ain't broke we haven't added enough features.

      Actually Gnome suffers from the opposite problem - if they think something is too complicated for a user (such as, say, the impossibly challenging job of selecting options for your screen saver), they usually rip it out. According to them, they should do all the thinking for the user.

    10. Re:Stop Screwing with the Interface... by thegarbz · · Score: 1

      If it' ain't broke, don't fix it.

      The horse and cart weren't broken. Neither was the old mobile phone. Don't confuse "fixing" something with simple technological development, especially when your opinion is completely uninformed.

  8. My father by Anonymous Coward · · Score: 0

    So how do I now get my father to understand this enought to use it. It's was hard enough teaching him how to use the back button and the task switcher button.

    UX is gone out the window with phones these days...

  9. Android Pie is shitty by Anonymous Coward · · Score: 0

    Noticing a trend with Android where updates make the phone shittier and buggier. Stop with this nonsense.

  10. Is this new? by willoughby · · Score: 1

    I've been doing this on my Moto G5 Plus for almost two years. I think some of the other Moto models also work like this. Is Lenovo really that far ahead of other Android companies?

  11. Obsessive minimalism is mental illness. by Anonymous Coward · · Score: 2, Insightful

    It stems from the same "philosophy" as Zen buddhism, whose point is to reach "nirvana", where you havd completed abolishing your own existence "from this universe". Where all joy and purpose is done away with, in favor of the ultimate goal of doing away with the frightening overwhelming reality.

    That this is harmful, is obvious to everyone.
    Like in this case, like nearly all K.I.S.S. / " simplicity" / minimalism cases, where the new version is *more* cumbersome than the old version.

    Yes, I want life to not be hard too. But I do not want to lose power and actually having a life in the process!

    1. Re:Obsessive minimalism is mental illness. by Fly+Swatter · · Score: 3, Insightful

      If you look at it from the perspective that all these phones and tablets are 'consumption devices'. Well, they want to make it more and more like a TV, such that you don't really have much control to skip content or advertisements. You can pick a channel (app) and now just watch your entertainment and whatever ads they want to show you.

      Clearly being a portable TV is their end goal, not a portable computing device.

    2. Re:Obsessive minimalism is mental illness. by Anonymous Coward · · Score: 0

      Tim Cook, is that you? How does that faggot dick taste?

  12. The old flight simulator issue by SuperKendall · · Score: 1

    Especially "to the left" which always implies 'forward' to me...

    I agree with you, but I can see the thinking where they think you are pushing thing backwards.

    It almost seems like they need a setting that most games have, "invert look" where anyone who set it would be able to swipe towards the right to go back.

    --
    "There is more worth loving than we have strength to love." - Brian Jay Stanley
  13. Accessibility by Hydrian · · Score: 2

    What about accessibility issues? A button press is a lot less movement requirement than a swipe.

    --
    No good deed goes unpunished.
  14. It's all about AMOLEDs by Stormwatch · · Score: 2

    These days they're really pushing AMOLED screens. Which is a GODDAMN FUCKING RETARDED IDEA because those damn things are too susceptible to burn-in. And this is especially noticeable in the areas where there is a static image most of the time -- such as the on-screen buttons. So, by getting rid of those, they mitigate this problem a little. Of course, the correct solution would be to not use AMOLED screens.

    1. Re:It's all about AMOLEDs by Anonymous Coward · · Score: 0

      I have two fairly old OLEDs, a first-gen PS Vita (which I still play 2-3 times a week) and an HTC incredible (works but shelved), and neither of those OLEDs has any burn-in. The Vita does have a random blobby region that shows a very deep/dark reddish tint when the screen is on but showing black (so the pixels should be off) though. Not that noticable.

    2. Re:It's all about AMOLEDs by Stormwatch · · Score: 1

      My experience: three fairly old phones here - Note II, S5, Nexus 6 - all with noticeable burn-in and yellowing.

    3. Re:It's all about AMOLEDs by Anonymous Coward · · Score: 0

      I keep seeing you people complaining about AMOLED screens and yet my Samsung S5 mini from mid-2014 is working flawlessly. But then again, I don't live with my phone in my hands, so maybe I'm the problem...

    4. Re:It's all about AMOLEDs by thegarbz · · Score: 1

      These days they're really pushing AMOLED screens. Which is a GODDAMN FUCKING RETARDED IDEA because those damn things are too susceptible to burn-in.

      Errr no. Please stop repeating 5+ year old tropes. The last phone that suffered from burn in as a result of technological inadequacy rather than a poorly designed or made panel was the Galaxy S2. On AMOLED panels the problem has been largely solved many years ago. Even my 6 year old Galaxy S4 which I continue to use daily as a navigation device after retiring it from my main phone, which is on it's 5th battery thanks to constant use shows no sign of burn in.

      Get with the current technology.

    5. Re:It's all about AMOLEDs by Stormwatch · · Score: 1

      Got an S5 here that says otherwise.

    6. Re:It's all about AMOLEDs by thegarbz · · Score: 1

      Congratulations on getting a dud. There's several million out there that work just fine.

    7. Re:It's all about AMOLEDs by Stormwatch · · Score: 1

      Also got a Nexus 6... another dud?

  15. The display *will* break by Anonymous Coward · · Score: 2, Insightful

    Because you will flip your phone out of your hand and onto the ground when trying to perform such a gesture with your thumb positioned so low on the screen.

    Scrolling up and down is fine but gesturing left and right can get wobbly, especially on larger phones.

    1. Re:The display *will* break by Falos · · Score: 1

      unmod, AC has valid point about vertical v hortizonal rotation axis

  16. The Back Button is Already Broken by Thelasko · · Score: 1

    Since I was updated to Oreo, I noticed the back button doesn't work correctly anyway. Often times it functions as a home button instead. It's very frustrating when I'm trying to get to the home screen of an app, but it takes me to the home screen of the OS instead.

    --
    One of our competitors trademarked the term "hypothesis". From now on, we will call them "boneheaded ideas".
    1. Re:The Back Button is Already Broken by Ksevio · · Score: 1

      That's an app design issue though - some apps see "back" when they're at their home/root screen and decide that the only place back from there is outside the app.

    2. Re:The Back Button is Already Broken by Thelasko · · Score: 1

      That's an app design issue though - some apps see "back" when they're at their home/root screen and decide that the only place back from there is outside the app.

      That's not what's happening. Say I open my text messaging app, and it takes me to my last conversation. I push the back button to go to the home screen and select a different conversation. However, it takes me to the OS home screen instead. If I reopen the app, and press the back button I get the the test message home screen.

      Maybe it is an issue with the way some apps are written, but you misunderstood the issue.

      --
      One of our competitors trademarked the term "hypothesis". From now on, we will call them "boneheaded ideas".
    3. Re:The Back Button is Already Broken by AuMatar · · Score: 1

      BEcause you launched the app into a specific activity. Back doesn't mean go to home. It means finish() the current Activity and let the previous thing on the stack come up. Which if you launched it directly into the message activity is back to the OS or previous app.

      Think of it this way- if you hit the notification for a message, read it, and hit back, do you expect to go to the list of messages? No you expect it to go back to where you were previously, usually another app. This is what's happening. If you changed this, then notifications and similar flows would feel broken.

      --
      I still have more fans than freaks. WTF is wrong with you people?
    4. Re:The Back Button is Already Broken by Thelasko · · Score: 1

      Think of it this way- if you hit the notification for a message, read it, and hit back, do you expect to go to the list of messages? No you expect it to go back to where you were previously, usually another app. This is what's happening. If you changed this, then notifications and similar flows would feel broken.

      That scenario would be fine. However, that's not what's happening. When I open the app, it takes me to my last message. Perhaps that's the issue. It should take me to the home screen when I open the app. Since I want the home screen for the app, I hit the back button, for lack of a better option. In previous versions of Android, it took me to the app's home screen. In Oreo, it takes me to the OS home screen.

      Basically, I can't figure out how to get to my list of text message conversations. It feels like other apps have this problem, but I might be mistaken. It might be a problem with the app.

      --
      One of our competitors trademarked the term "hypothesis". From now on, we will call them "boneheaded ideas".
  17. He meant easier for the user. by Anonymous Coward · · Score: 0

    You know. The idiot who actually has to pay money for it.

    Which is of course a silly mistake.
    All that matter is how they can milk their livestock the most. Hail profit!

    1. Re:He meant easier for the user. by fluffernutter · · Score: 1

      So I'm supposed to know the ins and outs of how a phone work in the 10 minutes I'm standing with it at the kiosk?

      --
      Laws are rules for the court, but merely a bottom bar to hit for life. Think beyond laws in your actions always.
  18. Off-topic: Version identifiers by slipped_bit · · Score: 1

    Why every software project these days need to be identified by both a version number and some cutesy name? What's wrong with just "Android 9"? No, it has to be Android 9 Pie. I get that people doing internal work on things might have code names for unreleased versions, but once it's released those aren't needed anymore.

    But since we've already crossed that threshold let us go one step further. To differentiate possible versions of Android 9 Pie I suggest episodes of Seinfeld.

    "It doesn't work in Android 9 Pie That Time we Waited for a Table at a Chinese Restaurant."
    "Don't worry, they fixed it in Android 9 Pie Jerry Scratches his Face but the Woman he Wants to Date Thinks he is Picking his Nose!"
    "For some reason I can't update from Android 9 Pie The Contest, despite how much I swipe!"

    1. Re:Off-topic: Version identifiers by Ksevio · · Score: 1

      Don't really need code names if they're incremental. Obviously the people working on a dessert starting with Q (a quiche maybe?) are working on the upcoming android version.

      The benefits I see are it makes them easier to remember and more distinct, so people know just because an app works on "Marshmallow" doesn't mean it will for sure work on "Lollipop".

    2. Re:Off-topic: Version identifiers by slipped_bit · · Score: 1

      Just because an app works on version 6 doesn't mean it will work on version 5. That's easier / faster to comprehend (for me, at least) than Marshmallow and Lollipop, but then again I've been told I'm a bit weird.

      I'm just perplexed why people feel compelled say both the version number and the name, as the two are (basically) redundant.

      It's also interesting that when I normally question things like this (things that I find very odd, like calling a "daughter board" a "shield" in the arduino world, even though the word "shield" means something completely different in the rest of the electronics industry) I'm told it's because it's shorter and faster to say or type, yet in the case of Android versions it seems I'm the only one who likes the short approach while the rest of the world prefers the long approach. Android 4? No. Android 4 Ice Cream Sandwich.

    3. Re:Off-topic: Version identifiers by Ksevio · · Score: 1

      I've never seen anyone say the number along with the name like that - seems quite redundant.

      There's also the issue that some versions weren't full major versions so it's easier to say "Kitkat" than "Android 4.4.0".

      LineageOS renumbers the releases so "Pie" is LineageOS 16. That seems to clear it up a bit more, but I can see why they'd want the sub-versions in the main version.

  19. And that is evil and wrong. by Anonymous Coward · · Score: 0

    You are correct.

    It's called vendor lock-in. And like any other form of monopoly, it is a crime.
    And them literally being the lawmakers is the only reason they don't go to prison.

    Well... for now.

  20. No!!! Don't take my button! by darth_borehd · · Score: 1

    It works fine and has been one of the best reasons to get an Android over an iPhone X.

  21. ORLY by jf_moreira · · Score: 1

    I am not sure but I think I have been using these type of gesture in my Moto 5 in the last two years. Swipe left to go back, swipe right to show running apps. There is a fingerprint sensor involved, and no other physical buttons.

  22. Can We Trust The Apps Programmers? by Anonymous Coward · · Score: 0

    "...a back button appears only when it's needed."

    Yes, but can we trust the apps programmers to display that back button? Contained in this are the seeds of modal interfaces; which we abandoned (quite rightly) a long time ago.

    Just imagine this line of app design reasoning: We don't want the user to be able to back out. Once we present them our Can't Get Enough, Whiz Bang, Awesome Sauce account signup screen, there should be no way back! Only losers would want to bail out on our fantastic ecosystem and we don't support losers. Forward only!

    Sure, you can close the entire application. For now. Until they find a way to disable that too. Which could be done and justified by, "the users asked for this capability." All you have to do is define the app owners and programmers as being "the users of interest".

    I'm not sure the software will develop in this direction but I'm wary that it might.

    1. Re:Can We Trust The Apps Programmers? by Anonymous Coward · · Score: 0

      iPhones don't have a consistent back button. Odd to say but that's the "killer app" that keeps me on Android.

  23. Counterintuitive by Dan+East · · Score: 1

    The "back" gesture (dragging the pill from the center to the left) for use within an app to go back is counter intuitive. Gestures should represent the physical motion matching the virtual motion. For example, you swipe your finger downwards, and the image moves downwards (which is logically "up" as you are going back up to the top of the document). Since we are accustomed to a side to side flow where older items are on the left and newer is to the right (based on LTR reading, calendars, page orders in books, etc)), a dragging motion to the left is backwards. That should scroll the display to the left, which reveals new content coming in from the right. So this new "drag the pill left to go back" is totally backwards. Apple solved this by introducing a gesture starting at the very leftmost edge of the display swiping to the right, which drags the entire display to the right revealing the previous / older item coming from the left.

    --
    Better known as 318230.
  24. Actually pretty good, TYVM. by Anonymous Coward · · Score: 0

    The more faggy, the more girly the shower gel and perfume.

    Unfortunately, sissys also have quite small dicks. To small to even make me gag right. Let alone fuck my ass enough to prolapse. I always have to make them punch fist me.

    Except for that big black bongo with the perfect skin. Infortunately they rarely make for very sexually ambiguous sissies.

    Did that answer your homo-curious question?

  25. No, because the only intuitive interface is ... by Anonymous Coward · · Score: 0

    ... the nipple. Everything else is learned.

    This is more about maximising "emergence". The amount of power you get from the amount of skill you need to get.
    E.g. "everything is a file" combined with CRUD is amazing. Because no matter what you are handling, as soon as you know the few basic operations (lookup/dir, create/ delete, write/read/copy), you can handle ALL the structures and interfaces and whatever that are implementing the file system interface.

    Which is insanely much better than requiring that "there's an app for it" for every permutation of combinable funtionalities.

    1. Re:No, because the only intuitive interface is ... by Anonymous Coward · · Score: 0

      Nipple is the only True Scotsman intuitive.

      A pedant might argue on "more/less intuitive" for keeping to supercommon real world analogues and adhering to practices universal in tech and UIs.

      Everything Is A File, for instance. Organized containers, including nesting.

    2. Re:No, because the only intuitive interface is ... by fluffernutter · · Score: 1

      Last I checked, I was the customer not the lab rat.

      --
      Laws are rules for the court, but merely a bottom bar to hit for life. Think beyond laws in your actions always.
  26. People will... by rnturn · · Score: 1

    ... get seriously pissed off if phone OS developers start making changes like this. At least that's my prediction. You develop a degree of muscle memory after using a phone for a while and it's an annoyance to have to adapt every time a phone developer gets a crazy idea that'll get rolled out without any idea of disruptive it is to the end users. Just because it's "new" and "innovative". What's next? Making Dvorak the default keyboard?

    --
    CUR ALLOC 20195.....5804M
  27. Xiaomi MIUI 10 Gestures by Nieriko · · Score: 1

    I have got addicted to Xiaomi MIUI 10 gestures. I think they really got something right in their implementation. Drawn in the lower half of screen: full swipe left/right equals back button press, swipe up equals home, swipe up and stay in the middle brings up the recents menu, drawn in upper half of screen swipe left/right triggers app action. I hope these gestures become a standard so there are available on all handsets.

    1. Re:Xiaomi MIUI 10 Gestures by Anonymous Coward · · Score: 0

      I used to own a smaller Sony phone, and I had an easier time reaching for the buttons at the bottom of the screen. When I switched to a Pocophone F1, with its massive 6-something inch screen, I simply can't be assed to reach for the bottom anymore when the UI elements I'm interacting with are already somewhere up top or in the middle. In addition to those gestures, the app switch gesture is really useful as well.

  28. Android is shit for game devs by Anonymous Coward · · Score: 0

    How many existing games get ass fucked by this new mechanic?

  29. I've got a gesture for you by Anonymous Coward · · Score: 0

    Yeah, that's right, the bird.

  30. Windows Phone interface by DogDude · · Score: 1

    Part of the reason (but not the entire reason) that I still use a Windows Phone when I need to use a smart phone is that the interface is really good. I have an Android phone for testing, and I've used a relative's iPhone, but those are both messes compared to the Windows Phone.

    --
    I don't respond to AC's.
    1. Re:Windows Phone interface by roc97007 · · Score: 1

      Um, so how does that relate to the current topic? I'm genuinely curious -- what does Windows Phone use for a back button? I haven't touched a windows os on a phone since Windows Mobile 6, and that one tried to have a start button and walking menus on a phone. Horrible experience.

      But as bad as that was, it wasn't the reason I got rid of the phone. The last straw (of many) was when the audio driver would die, sometimes silently, and sometimes helpfully with a little popup "the audio driver has caused a problem and will now close. OK." And the phone would not ring until it was rebooted. Being on-call with a phone that randomly stops ringing on incoming calls is not a good thing. I never considered Windows for a phone again.

      --
      Oliver's law of assumed responsibility: If you're seen fixing it, you will be blamed for breaking it.
  31. Just keep the OPTION open by p51d007 · · Score: 1

    I prefer the old style navigation buttons. I don't care for something FORCED on me. Just leave the option to change it. I mean, make it the default, but allow it to be changed back. But, Google is starting to wall stuff off and making a locked down garden.

  32. Do both by roc97007 · · Score: 1

    At least for now, do both. Allow the new gesture but keep the button. Let us get used to the gesture and explore how individual manufacturers will screw it up. If the gesture becomes popular, then and only then remove the back button.

    ...in other words, not at all like new gui features are usually introduced. ("Yeah, we changed it. Live with it.")

    --
    Oliver's law of assumed responsibility: If you're seen fixing it, you will be blamed for breaking it.
  33. Lenovo by Anonymous Coward · · Score: 0

    Lenovo Chinese Android phones don't have a back button, you just tap the home button, and clicking the home button is home, holding a tap is to see all running apps.

  34. Switched from Apple to Android 8 years ago by AbRASiON · · Score: 1

    I did this SPECIFICALLY because I was so impressed with the consistency of the back button location, the fact I could access context menus consistently with the settings / context / right click button.

    . They've gone on to ruin the options / context consistency, for a multi task button.
    They have removed my home button.
    They're (generally) copying Apple with the headphone jack.

    Now the back button? UI / UX designers peaked about ten years ago. Now they just break stuff to keep working and "innovating"
    So so so so sick of stupid ui decisions the last decade. Across the entire industry.

  35. Immaturity by tobyp · · Score: 0

    There is a reason why there is an age limit on becoming President of the USA. However *smart* you are, wisdom always takes time to develop. And one sign of wisdom is not too change things for the sake of change. Imagine if the UX designers were unleashed on the car industry, we'd be steering with pedals (it's so much more intuitive!) and braking with a lever (focus groups really liked it!). A consistent interface is better than a volatile interface: QWERTY vs Dvorjak etc, telephone and calculator button layout etc.

  36. Because non-techies like names more than numbers. by couchslug · · Score: 1

    That's why. The core audience for phones is the average trifling consumer, not techies.

    Too bad not enough techies are willing to buy Linux phones for development to pay off. Android is broken by design and Google likes it that way.

    --
    "This post is an artistic work of fiction and falsehood. Only a fool would take anything posted here as fact."
  37. Alternatively by Anonymous Coward · · Score: 0

    Perhaps, in the next release, they could free up even more screen real estate by triggering some of the actions through a smell. In order to return to the home screen, the user would simply generate a woody, slightly musky smell; to show running apps the user would emit a sharp, fruity odour and to start Chrome the user would simply exude an acrid ammonia-like fragrance.

  38. Moto G by markdavis · · Score: 1

    >"Android's back button might be going away entirely, replaced with a quick swipe to the left from the home button."

    I have already been doing this on my Moto G5 for a very long time. You can change the fingerprint thing to be a back button by swiping to the left and home by tapping it. This removes the on-screen buttons that rob space. It seems to work relatively well. But it is NOT intuitive for someone like my Mom....

  39. Zaphod by segwonk · · Score: 1

    Immediately thought of this scene from one of the Hitchhikers Guide to the Galaxy books:

    "A loud clatter of gunk music flooded through the Heart of Gold cabin as Zaphod searched the sub-etha radio wave bands for news of himself. The machine was rather difficult to operate. For years radios had been operated by means of pressing buttons and turning dials; then as the technology became more sophisticated the controls were made touch-sensitive--you merely had to brush the panels with your fingers; now all you had to do was wave your hand in the general direction of the components and hope. It saved a lot of muscular expenditure, of course, but meant that you had to sit infuriatingly still if you wanted to keep listening to the same program.
    Zaphod waved a hand and the channel switched again."

    --
    - ------ Go 'til ya know.
  40. cannot ruin android enough by Anonymous Coward · · Score: 0

    Ugh! Google should fix what is broken first.

  41. UI designers are a cancer by nightfire-unique · · Score: 1

    Not much else to say.

    --
    A government is a body of people notably ungoverned - AC