The issue is really a catch-22 usability testing rather than saying 1 way works better than another.  On mobile app&#x27;s you have more screen real-estate to play with, while in the browser you have less.  A website with a header anf floating footer cause many site&#x27;s to become un-readable and un-navagatable.  You then have the issue of responsive design that allows for the bun to come into play nicely rather than having to change a site&#x27;s design to fit within multiple viewport sizes.  I get the argument in a mobile application, but in a browser-based site you are left with either mystery meat, leaving out part of the navigation, or changing a responsive design completely to allow for easier mobile navigation.  Options are limited and purely based upon time and budget - and even then it&#x27;s a geusing game without proper split testing.