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?
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
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.
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.
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.