3 ms·
As a developer I am a big fan of Bootstrap, as a user I am starting to hate it however. Previously for mobile versions of sites they would simply check the use
by Someone1234 12y ago
As a developer I am a big fan of Bootstrap, as a user I am starting to hate it however.
Previously for mobile versions of sites they would simply check the user agent and if you had a mobile browser they would display the terrible/broken/useless mobile site (e.g. m.example.com). Most mobile browsers built in "Display Desktop Site" functionality to fix this problem.
However now with Bootstrap instead of using the user agent they use the screen size. So "Display Desktop Site" is ineffective and you're left using the terrible/broken/useless mobile site (which still has missing content, breaking content, and dead links even using Bootstrap).
This type of thing is the main problem:
http://ageekandhisblog.com/css-how-to-easily-hide-content-on-only-mobile-or-only-desktop/ http://ageekandhisblog.com/css-how-to-easily-hide-content-on...
The main issue with Bootstrap is that escaping the mobile version is almost impossible.
- k-mcgrady 12y agoThat's not the fault of bootstrap, it's the fault of developers. They're taking the easy way out by using bootstrap to easily create a mobile site and they won't even take the time to do a little customisation to make it work correctly with their content. They could easily disable the responsive features. It's lazy development.
- krisdol 12y agoI agree with you and minimaxir, but it doesn't change the fact that the websites are still unusable. As a user, I'd like to still have a way around the developer's mistakes. I wish it were easier for mobile clients to fool the site into thinking it's on a different screen size or aspect ratio.
- emodendroket 12y agoIt's bizarre because the path of least resistance is really to "let Bootstrap do it" and just have it reflow the content for different screen sizes.
- minimaxir 12y agoThat's more a failure of QA than a failure of design. Blogs in particular have elements when tend to break responsive layouts.
- soapdog 12y agoNot wanting to change the way you work but the whole responsive design movement and the mobile first approach are king for web development these days. User agent sniffing was always a bad practice and thats why Chrome and friends still need to refer to themselves as Mozilla/* If you code using responsive design, not only your site will work on mobile devices and desktop but it will also work in future aspect ratios. Lots of people were doing pixel perfect design on mobile sites for iPhone but when that iPhone 5 came in with the new resolution all those designs broke. Blackberry Passport device uses an rare 1440x1440 resolution, if you do pixel based alignment or fixed layouts you will be in trouble in all those marginal devices that together amount to a large percentage. Specially when dealing with Android devices. So if you begin from the start using bootstrap the way it is meant to be used which is by following a responsive design paradigm then you can forgot the clunky hack that is "display desktop site". Instead com arguing for a agent sniffing solution, we should all be coding for resolution and depth independence. Your main issue about bootstrap and escaping mobile version is antagonist with the way it should be used. There should not be a mobile web and a desktop web. There is only one web and media queries are your friend. If you know all this I am talking about and that would be pretty normal since I spoke nothing but common knowledge, then you know that user agent sniffing and mobile version of sites are all legacy stuff. Coding with modern practices is much easier and less trivia filled than it used to be.
- ceejayoz 12y ago> The main issue with Bootstrap is that escaping the mobile version is almost impossible. This is why iOS8 added a "Use Desktop Version" feature to Safari.