Apollo with both left and right swipes disabled and Disable Navigation Gestures turned off used to let you swipe left to right as “back” after reading a post (or a link in the built in browser) and then swipe right to left “forward” to return to it.
Voyager is an excellent web app, really enjoying it and looking forward to a native app in the stores.
I am now having trouble swiping on the list of posts to go back. The trick of swiping from the very farthest edge only works on the comments list now. I thought it was working on the list of posts up until recently. Maybe it’s the different native apps I am testing.
I do have a Lifeproof case. I am not giving it up as it saved my phone just yesterday from getting wet. Just getting a little frustrated with all my accidental voting and replying.
I like the current one but I voted for A if you have to change it. It looked the best on the desktop.
Not at present, this is something that Apollo supported.
So the link is for a request to the Voyager developers to look at implementing it in the future. If you know any programmers, share the project and see if they’re interested in helping!
You bet!
Really hoping this one gets some love, I had disabled the both left and right and left swipe gesture navigation enabled on Apollo and it made all the difference in my usage.
In all of the apps I am trying to use now I keep accidentally voting and replying and it’s frustrating. The apps all do something different. I know it’s my muscle memory that I need to retrain but changing apps as I test is making it take longer.
This feature was just genius because it let everyone decide for themselves what a swipe would do or not do.
There is a request at the source repository for this feature,
Good News everyone! I do feel welcomed into the future, this is my first post. I finally got signed up after I found wefwef and knew it was the missing link and now I could enjoy the fediverse.
I didn’t even try going to the official app. Oh my no.
This would be ApolloParity and I know Memmy has implemented it. Is there an issue in GitHub yet? I can post screenshots if that’s helpful.