You know how stressing it's to tap the "back button" unknown times to close a given application.
As most of the āback buttonsā it navigates you back to the recent item in the history stack, oh wait... you may not know which item or page is on top of the stack hence visiting an unintended page.
If you're an Android user or ever owned any gadget running Android os you're familiar with "back button" always (99% of all the time) placed at the button right of the phone/gadget.
You know how stressing it's to tap the "back button" unknown times to close a given application. The os doesn't communicate the number of many times required to close the application successfully Having a functionality to close the application was a wrong choice by google, take an example if your browser "back button" could close the browser that would be a total mess.
Then it gets even worse, that after closing the application and landing on the homepage it keeps toggling between you screen pages. The button performances all the above-stated actions behaviours 90% all the time without changing form or colour to communicate what the next action is.
The browser's "back button" is not as messed up as that of android os, it only performs one action "to take you back to the previous page".
Take this example; You have three tabs open on your browser, then you leave your work station for about one hour, coming back to open one tab by then you would have forgotten what the previous page was, and blindingly you can use the back button to go back. Still, you won't know the page to land on till it opens
This is a simple as it sounds; not relying on the browser's "back button" and:-