3 ms·
No, it doesn't have to be that way, and on mobile devices it often isn't. In a mobile browser a lot of this layering is invisible or only available when called
by jameshart 15y ago
No, it doesn't have to be that way, and on mobile devices it often isn't. In a mobile browser a lot of this layering is invisible or only available when called upon by the user. And consider also whether this excessive contextualisation might have something to do with the success of the 'app' model for accessing services, where the device focuses solely on the task at hand and all that framing goes away completely.
- dsr_ 15y agoMobile devices have their own UX expectations, and a browser has to fit into that model. You don't get a titlebar plus minimize/maximize/kill buttons because that's not the metaphor that the device uses. If everything on your desktop has a titlebar + buttons, your browser had better have those as well, or else it's a distraction. Don't break the metaphor. Use local system libraries. Don't make maximizing the window a surprise. If you want a nonframed experience on a desktop, it can't be the default. You can make it as easy to access as one keyclick to enter kiosk mode. Better provide a clean way of exiting, though, and best is to tell the user how to exit when they enter. (Take a YouTube video fullscreen, FF reminds you to 'Press ESC to exit'.)