The left/right swipe actions are used in a lot of android apps. It might be nice to disable the sailfishOs gestures in certain regions of the screen to allow for android apps to retain some of their functionality.
For instance, the top 2/3 of the screen could be for android app gestures, the bottom section for Sailfish.
until suitable replacement apps are created I continue to rely on Android apps, so having their functionality be somewhat limited is a bit tedious.
No, this would make it even worse; the meaning and purpose of swipe would be lost. The real question here is when that triangle, which appears in every app and cannot be removed, will finally disappear. The second question is, when you become famous tomorrow, what kind of swipe system will you bring to every app? That could become a bit problematic. The reason they donât remove that triangle is already related to this.
You mean the back button? Iâd also like to see that gone. Or customisable at least. Thereâs ample room at the top of the screen between the cameras. Iâd like to see it moved to there. Then it also matches the Sailfish back button.
I agree to some extent, but maybe thereâs a compromise. A two finger swipe across the screen defaulting to the android swipes. It also might be nice to just have it as a toggle. By default, off, but I should be somewhat in charge of it.
Some of this will indeed be muscle memory.
They donât want to remove the back button for now, because even on Instagram thereâs no swipe gesture. In quite a few social media apps, thereâs no gesture for going back or switching between screens, so you canât do it by placing your finger in the middle of the screen and swiping. Fixing that is really difficult.
Iâm also really annoyed by the triangle button at the bottom. I tried to remove it, but unfortunately, because the software is closed-source, it wouldnât let me customize that part of the code.
There are two ways this could be solved: Android is almost at its latest version, so swipe gestures will gradually start coming back in every app, since theyâll eventually support the newest Android version, or theyâll have to turn each one into a native app. 
Let me put it this way: if they make it as transparent as you described, as far as I know, emulator apps arenât allowed to customize that part, so they canât really change it.
There was aliendalvik-control by @coderus which could hide the back button and add gestures, but it is long outdatedâŚ
There were also some patches and applications to hide the bar.
I tried this while attempting to remove it, but it didnât work. I even built it myself, yet it still wouldnât allow me to customize it. I think this method may no longer be valid, or perhaps I was making a mistake somewhere. It probably used to be supported in the past, because I also developed an app using the same approach.
However, as I mentioned, no matter how much code I write, I still canât access the Android system layer. I also tried to solve it through Aurora Store. They can change the icon, but it doesnât work very efficiently. Unfortunately, theyâre the ones who need to fix this issue.
Sad thing on that back button is that here are several android apps that donât need that (nor a swipe gesture) while others like discord have a dedicated own back button. Would perhaps be useful to have an option in AAS settings in which android apps the back button is not necessary.
For me that doesnât use Android (and rather few AAS apps); these are just back-gestures, right?
Then why not use the button?
Sailfish back button - sheesh.
It is the âthis page can be swiped to go back indicatorâ.
It is not meant to be tapped under normal use - iâm pretty sure that in the beginning it wasnât tappable. Though at some point it was made tappable to placate newcomers or people that only understand buttons.
Was this necessary? Iâm sorry that I didnât use the right nomenclature, but Iâm fairly sure you knew what I was talking about. I was saying it because thereâs a lot of space up in the top left corner where this could be.
Not always. Theyâre contextual. For instance, a swipe on something like Spotify or Deezer might be to add a song to a queue. I have closed the deezer application by doing this a few times.
It also is quite large, for what it is.
Yeah, some ppl skip the tutorial and then end up tapping the âexistence of backpage indicatorâ as if it was a button, no joke (I guess the plague that is a back button in top left of a ton of android apps just gives them such expectation, industry standards)
Thatâs not the point i wanted to make - i understood what you meant perfectly.
You said a button fits next to this other button and that it is logical because of that. But it is not a button. It is never meant to be tapped. And it is extremely unergonomic - nothing to strive after being similar to.
Actually on or from-outside-swipe? Because on should work and not be conflicting, shouldnât it?
You mean minimized?
I just tried that on Spotify, and I could still execute the swipe to add to queue correctly with my finger starting on the left of the album cover, which is maybe 3 mm from the edge of the screen. So it sounds like youâre just used to swiping from the edges for gestures that can be executed anywhere on the horizontal plane. Youâll get used to doing it like âusâ after a while!
Not exactly never, it still functions as a back button and if some app developer throws at you say fullscreen mapview it is a way to escape endless scroll left (which is also why browser doesnât use it, too many sites would be broken with that swipe acting as back button)
Perhaps not strictly; but this worked even before they became clickable, by swiping up there.
Rounding error anyway.
Iâm of the opinion that that just means the app is designed wrong, and either that map view should be page 1 or there should be a different kind of button lower down on the screen to move to a different page. Or both, as Pure Maps quite nicely does.
I would prefer a footer/pager combo you can swipe over than buttons, but yeah this definitely a case of developer neglect and ideally doesnât happen, but in browser you get such things all the time, open google maps and try to move viewport bit to the left, youâre back to your previous page, button there makes perfect sense
You mean like how Firefox (mobile) allows you to swipe over the address bar to go back/forward? Yeah, I could definitely get behind that.
Yeah, they also should move keyboard switching to swiping over spacebar, itâs way too aggressive on J2, but weâre veering OT
One day, when weâre in a relatively updated state I feel there needs to be a refresh of some of the gestures in the stock browser.
I would prefer switching tabs with a swipe over the address bar, and I think pull down to refresh works well without interfering with the OS gestures.
And maybe we could look at some of the gestures listed here for some other ideas.
There are always some (new) people who propose adding some Android behaviour to Sailfish, which is understandable - they moved to a new platform and would like it to work how they are used to.
But Iâm personally against adding Android-like stuff to Sailfish. Sailfish isnât just a privacy OS that can run Android apps (you can already achieve the same with some custom ROMs like GrapheneOS or /e/OS ). SailfishOS is its own operating system with its own UX design principles and many of us are here rather for that than for the privacy stuff. Adding more Android-things to Sailfish would just take away more and more of SailfishOSâes iconic own design (and in my opinion would make the UI/UX worse in general)