• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Suggestion for Enhanced Back Swipe Gesture Function - iOS like?

deejaawoo

deejaawoo

Newbie
Why can't a SINGLE back swipe gesture close the keyboard and go to the previous screen? like how it is on iOS

Example: when you're on an app like Instagram or Whatsapp.while typing the keyboard is open. we need to swipe back "twice" to go back to the previous page.

1st to close the keyboard
2nd to go back to the previous screen.

Solution: Swipe back "Once" it closes the keyboard and goes to the previous screen. And to close the keyboard we already have a tiny button below the keyboard to do it.

For people who want to collapse keyboard:
There's a dedicated small button on Samsung/Swift Keyboard to do the same ... It will collapse the keyboard only... On OnePlus there's a small black bar in the bottom for this.

Or

a simple Swipe Down gesture on the keyboard can collapse the keyboard. On OnePlus there's a small black bar in the bottom for this.

Thanks


Can someone help me implement this? probably by an ADB command or a Tweak? that changes back gesture to close keyboard if opened?
 
steiny180 said:
A single swipe will prevent you from going back to the current screen.

Am I missing something here?
Click to expand...

A single swipe will just close the keyboard ... to go back you need to make another swipe ....

whereas on iOS a single swipe closes the keyboard and goes back too...

That's what i want to bring into notice... it could improve navigation

Do have a look at the video ... Any help would be highly appreciated ... Thanks for replying
 
I think that whether it is an improvement is subjective. With most people not being accustomed to what you describe I'd guess that most would not regard it as such - the frustration of being thrown into a different app would be considerable.

Anyway I can't help with this, but suspect it might not be as simple as you hope (changing system behaviour), and would certainly depend on android version: the "back swipe" gesture only exists in Android 10 (or if a manufacturer has tweaked their version of Android), and even then it's optional (I don't use it as I find the Android 9 style more efficient and less prone to error or interfering with other apps).
 
Hadron said:
I think that whether it is an improvement is subjective. With most people not being accustomed to what you describe I'd guess that most would not regard it as such - the frustration of being thrown into a different app would be considerable.

Anyway I can't help with this, but suspect it might not be as simple as you hope (changing system behaviour), and would certainly depend on android version: the "back swipe" gesture only exists in Android 10 (or if a manufacturer has tweaked their version of Android), and even then it's optional (I don't use it as I find the Android 9 style more efficient and less prone to error or interfering with other apps).
Click to expand...

Hey thanks for the reply
We have moved from buttons to touch to corner gestures... So i guess we can easily say people adapt to something new ... specially when the change is not major...

The only small change here is to autoclose KB while going back.

a small tutorial can be given on the android gesture page and people will get habitual to it in few days.

Eg. People got habitual to do swipe up to go to home screen

OR

People got habitual for left corner swipe to open the hamburger menu.... but once the back gesture was introduced now many people enjoy the back gesture instead of the hamburger menu.

I was wondering if any ADB command can do the same?
 
I'm sure no adb command can change a system behaviour. The question is whether it's possible to write an app to override it (which may require an adb command to grant permissions).

But you are assuming that what you are familiar with is better. It's not a given that people who haven't spent a lot of time with recent iOS will feel the same. Back button = lower keyboard dates back to the very beginning of Android, and an inadvertent app change is far more annoying than having to tap or swipe something twice, so the downside for people who don't share your background is larger than the downside for you.

But the other thing to consider is that Android already has ways of swapping app without lowering the keyboard, the thing you are trying to achieve. They just don't involve the back gesture/button. So what you suggest doesn't provide anything that Android doesn't have already, it's just a different way of doing things. So it really is just trying to make things familiar to you, but less familiar to long-term Android users.

As an aside on the change to the current gestures, actually I'm quite critical of Google's UI choices. It's not just the hamburger side bar gesture they interfere with, but many apps use side-swipes to move to different pages (e.g. next article, or even next home screen), and the "swipe from the edge to go back" gesture interferes with this too. The "swipe up for home, swipe and hold for recent apps" is slower and less fluid than the Android 9 "press button for home, swipe for recent apps" and can clash with "swipe up on dock for app drawer". It's possible to use it, but it makes everything fiddlier than it used to be and hence harder to use quickly and reliably. I've read Google's notes on the gesture UI design, but they have overlooked several aspects of usability (I personally think because they were too influenced by Apple's gestures, which given the different UI features, such as Apple lacking an app draw or a real equivalent of the "back" action, was a bad approach). I have used the gestures for weeks at a time, but even with familiarity they never achieve the speed, reliability and fluidity of the previous system. Hence I have now stopped using them for as long as I have that option.
 
Hadron said:
I'm sure no adb command can change a system behaviour. The question is whether it's possible to write an app to override it (which may require an adb command to grant permissions).

But you are assuming that what you are familiar with is better. It's not a given that people who haven't spent a lot of time with recent iOS will feel the same. Back button = lower keyboard dates back to the very beginning of Android, and an inadvertent app change is far more annoying than having to tap or swipe something twice, so the downside for people who don't share your background is larger than the downside for you.

But the other thing to consider is that Android already has ways of swapping app without lowering the keyboard, the thing you are trying to achieve. They just don't involve the back gesture/button. So what you suggest doesn't provide anything that Android doesn't have already, it's just a different way of doing things. So it really is just trying to make things familiar to you, but less familiar to long-term Android users.

As an aside on the change to the current gestures, actually I'm quite critical of Google's UI choices. It's not just the hamburger side bar gesture they interfere with, but many apps use side-swipes to move to different pages (e.g. next article, or even next home screen), and the "swipe from the edge to go back" gesture interferes with this too. The "swipe up for home, swipe and hold for recent apps" is slower and less fluid than the Android 9 "press button for home, swipe for recent apps" and can clash with "swipe up on dock for app drawer". It's possible to use it, but it makes everything fiddlier than it used to be and hence harder to use quickly and reliably. I've read Google's notes on the gesture UI design, but they have overlooked several aspects of usability (I personally think because they were too influenced by Apple's gestures, which given the different UI features, such as Apple lacking an app draw or a real equivalent of the "back" action, was a bad approach). I have used the gestures for weeks at a time, but even with familiarity they never achieve the speed, reliability and fluidity of the previous system. Hence I have now stopped using them for as long as I have that option.
Click to expand...

Trust me bro i am more familiar with Android than with apple ... here is my phone history

Feb 12 2003 Nokia 6310i
2003 Nokia 1100b
2004 Nokia 7250i
2004 Nokia 7650
2004 Nokia Ngage
2004 Nokia 3650
2005 Nokia 6600
2005 Nokia Ngage qd
2005 Nokia 7610
2006 Nokia N70
2006 Nokia n72 Music Edition
2007 Nokia n73 Music Edition
14 July 2008 Apple iPhone 1 (2g)
27 Dec 2010 Apple iPhone 4
25 Jan 2013 Samsung Galaxy s3
25 June 2014 Samsung Galaxy s4
18 Feb 2015 LG G2
30 June 2015 Samsung Galaxy s5
24 Sep 2015 HTC ONE m8 Eye
1 Dec 2015 Apple iPhone 6
23 Aug 2017 One plus 5
21 May 2018 One Plus 6
19 May 2019 OnePlus 7 Pro

I keep switching during my work with my op7pro and iPad 6th gen. And i love how the iPad does "Back" really right... We are entering the generation of heavy texting back again... Currently it takes 2 buttons to go back... with this it'll take 1 button... Thus increasing productivity... I understand your point here... But we cant deny Android adapts from Apple .. and Apple adapts from Android both try hard to achieve the best UI experience.

Also I'm LOVING the changes Android is making.. many are still hating the gestures ... but I'm using the gesture related apps since Galaxy s5... it was then called Pie Navigation.

I LOVE my android phone ... op7pro is par excellent .. i just don't want to switch to iOS for one simple feature... i am a heavy texter thus i wanted this gesture that would close keyboard and go back when i click back button/ swipe from the edge.

Thanks
 
I don't know about using gestures for going back, my phone has a button at the bottom, that I tap to go back. And the last iPhone I had was 11 or 12 years ago now
 
Of course if you are using a OnePlus then you will have their gestures rather than Google's - which as I understand it are more extensive (and possibly better designed).
 
Now that app's description addresses one of Google's failures: making the side swipe only active on part of the edge makes it easier to avoid interference with other UI elements.

But failing to think that through, and failing to provide the ability for users to customise things for themselves (beyond a very limited "sensitivity" setting), is I'm afraid quite characteristically Google.
 
You must log in or register to reply here.
Back
Top Bottom