Mild guess. The dev(s) don't know about navigation buttons. Gestures have been "standard" for a while now so maybe someone forgot about this as a possibility?
Yes. You just swipe left from the edge of the screen to go back. You swipe up from the bottom to go to home. And a smaller swipe from the bottom, dunno how to describe it, for the square menu thingy. Easier than the buttons and you also gain extra screen space.
Oh...dunno. Mine's not that reactive to objects. I just tried touching my screen with a piece of cloth, even wrapping my finger in one and I still can't make it react.
Maybe it's just shitty phones ¯_(ツ)_/¯ either way though, if your feature makes my phone unusable it's def gonna trigger me. Obviously that's very self centered, but I believe accessability should be for everyone. Far too often devs remove beloved features from their software and it breaks so many legacy features.
I don't care about that small amount of extra screen space, and I don't like gestures, and I should have the ability to choose which solution I prefer.
I've found myself in a similar situation to OP, where a given app presumes that everyone is using gestures and conflicts with the buttons, and I don't appreciate it.
If this true this means they purposely ignore default APIs and reinvent the wheel. Android adjusts the viewport automatically in order not to overlap the navigation area, regardless of the actual navigation method. Sounds like incompetence
Oh snap! I've been putting up with this for over a year! I had no idea there was as a toggle. Why doesn't the android build installed from FDroid default to the android compatibility mode?
I tried this several times and even restarted the phone... Is restarted even politically correct anymore? It should be Sturptid or Durmt or Merntally Charlentged....I merntally charlentged my phone! And it still overlapped the buttons.
How the heck am I supposed to use the app if I keep clicking the desktop/main page? Actually, how is the desktop called on a phone? Hold that thought, its not useful to me rantnow! All I rant to do is rant!
Looks like the developer doesn’t know about the env(safe-area-inset-bottom) variable in CSS. Voyager is a web app, which is why it has this problem to start (I think), but that variable can be used as margin/padding to clear those buttons (and similar on other OS-es).
I wanted to build a universal web and native app. I started out using react native on iOS/Android and react on web. I realized that I was spending most if my time trying to get native to work as well as web. For example, the markdown renderers/editors on web are far superior to native imo. Making native a web app solves a lot of problems, but obviously it creates new issues like this post mentions.
The biggest issue with being a web app is I will likely never be able to get Liquid Glass working on iOS. I’m guessing same for voyager. But Liquid Glass kinda sucks, so we’ll call it a feature instead of a bug. I think these web apps can work around most other issues, including the one this post mentions.
This was last updated Mar 26, 2024 and the developer has been AWOL ever since.
Much as I love the app, Lemmy has gone through multiple API changes (and has more to come) such that staying on an outdated app isn't viable. Last I used it, it was already having issues loading pictures and comment threads.
This is it. The cat is a bit more heavy than it looks, and is pushing the buttons down into the bottom of the phone. Try feeding it some snacks filled with helium, the problem should disappear after a couple of days!
I just turned on Android buttons for the first time in 7 years to confirm your issue. Couldn't replicate. Either something wrong with your particular app (if full restart doesn't help try clearing data) or your ROM.
64 Comments
pedz@lemmy.ca · 54 pts · 186d
Mild guess. The dev(s) don't know about navigation buttons. Gestures have been "standard" for a while now so maybe someone forgot about this as a possibility?
PunnyName@lemmy.world · 23 pts · 186d
God, this might be why a certain micro rental car company in Los Angeles has the same problem in their app. Fuck them gestures!
Lost_My_Mind@lemmy.world · 16 pts · 186d
I gotta gesture for ya right 'ere, pal!
Denvil@lemmy.ml · 16 pts · 186d
People use gestures...?
nyctre@piefed.social · 6 pts · 186d
Yes. You just swipe left from the edge of the screen to go back. You swipe up from the bottom to go to home. And a smaller swipe from the bottom, dunno how to describe it, for the square menu thingy. Easier than the buttons and you also gain extra screen space.
Scubus@sh.itjust.works · 9 pts · 185d
Except when laying down and your blanket touches your screen and it loses its God damn mind.
Fuck I hate gestures
nyctre@piefed.social · 6 pts · 185d
Oh...dunno. Mine's not that reactive to objects. I just tried touching my screen with a piece of cloth, even wrapping my finger in one and I still can't make it react.
Scubus@sh.itjust.works · 3 pts · 185d
Maybe it's just shitty phones ¯_(ツ)_/¯ either way though, if your feature makes my phone unusable it's def gonna trigger me. Obviously that's very self centered, but I believe accessability should be for everyone. Far too often devs remove beloved features from their software and it breaks so many legacy features.
GraniteM@lemmy.world · 5 pts · 185d
I don't care about that small amount of extra screen space, and I don't like gestures, and I should have the ability to choose which solution I prefer.
nyctre@piefed.social · 9 pts · 185d
You do get to choose. That's what the settings are for. Someone commented the solution to the issue.
papalonian@lemmy.world · 4 pts · 185d
You're writing this comment as if someone just took your phone, changed the setting and removed the ability to change it back
GraniteM@lemmy.world · 5 pts · 185d
I've found myself in a similar situation to OP, where a given app presumes that everyone is using gestures and conflicts with the buttons, and I don't appreciate it.
user224@lemmy.sdf.org · 1 pts · 174d
And the you go on to use Termux, and encounter swipe from left to manage sessions.
franzbroetchen@feddit.org · 5 pts · 186d
If this true this means they purposely ignore default APIs and reinvent the wheel. Android adjusts the viewport automatically in order not to overlap the navigation area, regardless of the actual navigation method. Sounds like incompetence
village604@adultswim.fan · 4 pts · 185d
Nah, you just have to pick android or iPhone in the settings, which is just laziness on the devs part.
Don_alForno@feddit.org · 1 pts · 184d
It was fine until monday or so.
MrNesser@lemmy.world · 40 pts · 186d
Go to settings - appearance - theme- device mode (scroll down)
Select android or apple depending on your device
flubba86@lemmy.world · 27 pts · 186d
Oh snap! I've been putting up with this for over a year! I had no idea there was as a toggle. Why doesn't the android build installed from FDroid default to the android compatibility mode?
nutbutter@discuss.tchncs.de · 7 pts · 186d
Wow, this just fixed so many issues. Thanks!
Don_alForno@feddit.org · 2 pts · 184d
Doesn't fix it for me. It was already set to android, I tried switching to apple and back, it only changes the look of the menu, not the positioning.
altphoto@lemmy.today · -6 pts · 185d
I don't have this option available. ChatGPT makes up options that never actually existed. "Don't ask it how I know"
Nighed@feddit.uk · 7 pts · 185d
It's there! The theme sub menu is at the top, I missed it the first time.
altphoto@lemmy.today · 5 pts · 185d
Found it in a different location. It's set to the correct OS.
Nighed@feddit.uk · 3 pts · 185d
What version are you on? I'm on 2.44
altphoto@lemmy.today · 4 pts · 185d
Same version.
ummthatguy@lemmy.world · 19 pts · 186d
At first I thought this was a meme akin to not being able to get up because cat.
App devs have a tendency to not take into account mobile OS design. It's aggravating.
ttyybb@lemmy.world · 4 pts · 186d
Its not not a meme about not being able to get up because cat.
nevetsg@aussie.zone · 10 pts · 186d
Voyager does this to me occasionally. I just endtask it and re open.
serpineslair@lemmy.world · 6 pts · 186d
Try rotating ur screen landscape, then back to portrait, seems to temporarily fix it for me.
nevetsg@aussie.zone · 4 pts · 185d
Thanks for the tip. Will try next time.
Pyro@programming.dev · 2 pts · 182d
I second this, usually fixes it for me too.
altphoto@lemmy.today · 0 pts · 185d
I tried this several times and even restarted the phone... Is restarted even politically correct anymore? It should be Sturptid or Durmt or Merntally Charlentged....I merntally charlentged my phone! And it still overlapped the buttons.
swagmoney@lemmy.ca · 10 pts · 185d
I'm noticing this in more and more apps :(
altphoto@lemmy.today · 8 pts · 186d
How the heck am I supposed to use the app if I keep clicking the desktop/main page? Actually, how is the desktop called on a phone? Hold that thought, its not useful to me rantnow! All I rant to do is rant!
Rant this ranting rantotanter app!
Lost_My_Mind@lemmy.world · 6 pts · 186d
Do you smell toast?
over_clox@lemmy.world · 3 pts · 186d
I'm more concerned why there isn't an Outbox button, but I digress..
I don't have an exact answer, but have you tried turning the screen sideways?
altphoto@lemmy.today · 4 pts · 186d
Like this?
I also enabled gestures LOL fuck Android's buttons!
over_clox@lemmy.world · 4 pts · 186d
No no, I meant the cat is sitting on the inbox, if you tilt it to left, you might empty the outbox in the trash..
ollie@lemmy.zip · 7 pts · 186d
I have this issue but at the top of the screen. The title bar sometimes overlaps the time, notifications, etc.
I have the navigation buttons turned on at the bottom of the screen but I don't think I've seen this problem
Yucky_Dimension@lemmy.world · 3 pts · 186d
Rotating my phone's screen by turning it sideways temporarily 'fixes' this problem for me.
f314@lemmy.world · 6 pts · 186d
Looks like the developer doesn’t know about the
env(safe-area-inset-bottom)variable in CSS. Voyager is a web app, which is why it has this problem to start (I think), but that variable can be used as margin/padding to clear those buttons (and similar on other OS-es).MonkderVierte@lemmy.zip · 7 pts · 185d
Btw, any lemmy app that isn't a webrender?
owsei@programming.dev · 6 pts · 185d
Connect uses flutter, which I'm pretty sure isn't web render based
f314@lemmy.world · 3 pts · 185d
I’m on iPhone, so don’t know about Android apps, but Mlem is solid for iOS!
allan@lemmy.world · 3 pts · 185d
Jerboa
parzival@lemmy.org · 2 pts · 185d
I've been using blorp, AFAIK it isnt
moseschrute@lemmy.world · 3 pts · 185d
Blorp dev here. Blorp actually is too 😅
I wanted to build a universal web and native app. I started out using react native on iOS/Android and react on web. I realized that I was spending most if my time trying to get native to work as well as web. For example, the markdown renderers/editors on web are far superior to native imo. Making native a web app solves a lot of problems, but obviously it creates new issues like this post mentions.
The biggest issue with being a web app is I will likely never be able to get Liquid Glass working on iOS. I’m guessing same for voyager. But Liquid Glass kinda sucks, so we’ll call it a feature instead of a bug. I think these web apps can work around most other issues, including the one this post mentions.
poopkins@lemmy.world · 2 pts · 185d
https://play.google.com/store/apps/details?id=io.syncapps.lemmy_sync
LiveLM@lemmy.zip · 5 pts · 185d
This was last updated Mar 26, 2024 and the developer has been AWOL ever since.
Much as I love the app, Lemmy has gone through multiple API changes (and has more to come) such that staying on an outdated app isn't viable. Last I used it, it was already having issues loading pictures and comment threads.
poopkins@lemmy.world · 2 pts · 185d
Damn, you're right. Last update was exactly 2 years ago.
oopsgodisdeadmybad@lemmy.zip · 3 pts · 184d
Damn, how's next week looking, time traveler? Is trump dead yet?
poopkins@lemmy.world · 1 pts · 184d
At the risk of causing the universe to implode, I'm afraid I can't tell you.
FG_3479@lemmy.world · 3 pts · 186d
It works properly on my phone. Does the APK work?
altphoto@lemmy.today · 2 pts · 185d
I don't recall where I installed this one from. I think its form the googslop play store.
sorrybookbroke@sh.itjust.works · 3 pts · 186d
Wait, is that on purpose?
realitista@lemmus.org · 3 pts · 186d
Damn cat!
myotheraccount@lemmy.world · 2 pts · 185d
This is it. The cat is a bit more heavy than it looks, and is pushing the buttons down into the bottom of the phone. Try feeding it some snacks filled with helium, the problem should disappear after a couple of days!
altphoto@lemmy.today · 1 pts · 185d
Indeed!
atomicbocks@sh.itjust.works · 1 pts · 186d
Is this Voyager? Is it the Webapp or the App Store App? If it’s the Voyager webapp you may need to tell it you are on Android in the settings.
altphoto@lemmy.today · 1 pts · 186d
It's the Voyager app.
abfarid@startrek.website · 3 pts · 186d
I just turned on Android buttons for the first time in 7 years to confirm your issue. Couldn't replicate. Either something wrong with your particular app (if full restart doesn't help try clearing data) or your ROM.
altphoto@lemmy.today · 1 pts · 185d
I did both, then Restarted and logged back in.
abfarid@startrek.website · 1 pts · 185d
Then I guess it's your ROM...
Kalothar@lemmy.ca · 2 pts · 186d
What kind of android phone do you have?