Broken navigation?

[A Former User]

A Former User last edited by

What is the reason for IOS having "go back" button in quick menu and not Android? This really breaks the whole "for people on the move" vibe. And not only its not in the fast menu, the go back button in the right top corner can be pressed only once, before the whole top menu closes itself after you click it. So you need to repeat the whole slow process again. You don't want people to use go back option, or what?

The most logical thing would be customization option for the quick menu, where people could assign buttons they actually use. And for the love of God, option to turn off those annoying vibrations when using quick menu.

Touch is basically useless like this. When you can't navigate in any sensible way.

[themaciekk]

themaciekk Opera last edited by

Hi. There are some key differences between iOS and Android devices. We can't neglect them and applications need to adapt somehow. One of those differences is the back navigation. On Android you always have access to application manager, home and back button. You can use that back button to navigate back in history - you don't need to reach 3 dots menu.

On iOS you have built in navigation gestures (swipe from left and right edge to go back and forward), but it's convenient for all users, thus we decided to put back navigation in the FAB menu. This however meant we had to remove Reload action.

If you don't like vibrations, open settings and turn them off (this is android specific feature).