Having worked as a frontend web developer, I can assure you that the back-button hijacking is sheer incompetence of the developers. They have to be mutating your browser history in a careless way to achieve this. That or they somehow picked a really bad client-side routing library. (Even just following a basic tutorial for react-router wont cause this behavior. It's almost always sloppy state management causing this)
Well in this case it's the frontpage. That makes little sense. If it's further inside the application, it can become very difficult, but this is just when you click start now and you are stuck. That makes no sense.
