Hey! Why don’t we overlap buttons on purpose! What a great idea!
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?
People use gestures…?
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.
Except when laying down and your blanket touches your screen and it loses its God damn mind.
Fuck I hate gestures
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.
Go to settings - appearance - theme- device mode (scroll down)
Select android or apple depending on your device
Wow, this just fixed so many issues. Thanks!
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.
I’m noticing this in more and more apps :(
Voyager does this to me occasionally. I just endtask it and re open.
Try rotating ur screen landscape, then back to portrait, seems to temporarily fix it for me.
I second this, usually fixes it for me too.
Thanks for the tip. Will try next time.
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.
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).Btw, any lemmy app that isn’t a webrender?
I’ve been using blorp, AFAIK it isnt
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.






