I understand that "_the browser back button takes you back in history, not back in navigation_", and in some applications this can be confusing, but in a well-designed UX, where an "SPA" isn't trying to re-invent how the browser should behave, this should not be a factor.
More research is required and preferably a usability study should be conducted.
Once we have some more up-to-date qualitative/quantitative insight we should write a blog post on this.
Is having a Back Button (in your Web App UI) _good UX_ (progressive enhancement) ? #discuss
read these:
I found one UX question/answer that makes the case for back button: http://ux.stackexchange.com/questions/72769/do-we-still-need-to-add-custom-back-buttons-to-our-design but it only has one up-vote so don't take it as "truth"...
I understand that "_the browser back button takes you back in history, not back in navigation_", and in some applications this can be confusing, but in a well-designed UX, where an "SPA" isn't trying to re-invent how the browser should behave, this should not be a factor.
More research is required and preferably a usability study should be conducted. Once we have some more up-to-date qualitative/quantitative insight we should write a blog post on this.