6. Why Not?
Redundant elements and code downloaded to the client
Redundant data may be downloaded
Sometimes mobile pages need to look entirely different
8. Ways to do it
Screens for each device type
The same screen, looks different for each device type
9. Ways to do it (contd.)
Screen for each device Same screen, looks different
On server side, parse user agent Change styling according to device properties
Direct the user to another URL / Create another screen Relate only to device properties
Client side only
Pros Pros
More organized Less screens to maintain
Less elements to render No server side code
17. Viewport width related
font-size: 1vw; //1% of viewport width
font-size: 1vh; //1% of viewport height
font-size: 1vmin; //1% of the smaller dimension
font-size: 1vmax; //1% of the larger dimension
21. Bootstrap
CSS & Javascript library
Mobile first design
Built in media queries
Declarative and programmatic use of plugins
22. Bootstrap terminology
xs – Exrta small (Phones < 768px)
sm – Small Medium (Tablets, from 768px to 992px)
md – Medium (992px to 1200px)
lg – Large ( > 1200px)
23. Bootstrap visibility classes (from getBootstrap.com)
Extra small
devicesPhones
(<768px)
Small
devicesTablets
(≥768px)
Medium
devicesDesktop
s (≥992px)
Large
devicesDesktop
s (≥1200px)
.visible-xs-* Visible Hidden Hidden Hidden
.visible-sm-* Hidden Visible Hidden Hidden
.visible-md-* Hidden Hidden Visible Hidden
.visible-lg-* Hidden Hidden Hidden Visible
.hidden-xs Hidden Visible Visible Visible
.hidden-sm Visible Hidden Visible Visible
.hidden-md Visible Visible Hidden Visible
.hidden-lg Visible Visible Visible Hidden
33. We’ve started with an unresponsive app
Gradually added styles made it more responsive
Using HTML standards we can make our pages responsive
The same HTML & CSS can serve multiple device types
Our app still needs a designer’s touch
Well… I am not a UI guy
So…