Page 1
Using Responsive Web Designto future proof your Websites & Apps
Page 2
Emily DeereExec. Director, IT ApplicationsE: [email protected] : @edeere
• Stats• Mobile & UCSD• Organizational support
of central web services
Brett PollakDirector, CWOE: [email protected] : @brettcpollak
• Mobile framework• Transition to Responsive
Web Design• Looking ahead
Page 3
In about 2 months…
…there will be more connected phonesthan people in the world
Page 4
5 years ago, the iPhone didn’t exist…
…now it generates $100 Billion per year
Page 5
The iPhone is bigger than
Page 6
By the fall of 2013 more tablets will be sold than PC’s
Page 8
May 20102.19% of visits from mobile
Higher Ed. Home Page Visits
Page 9
May 20114.77% of visits from mobile
Higher Ed. Home Page Visits
Page 10
May 20129.82% of visits from mobile
Higher Ed. Home Page Visits
Page 11
112% average increaseyear over year
Higher Ed. Home Page Visits
Page 13
iPhone Application Launch - 2009
Page 17
Our UI Design needed a new approach…
User Interface was buried in middleware
Technology was aging
Developers wanted to use modern tools
Web App Development
Page 18
We hosted a competition!
Page 19
UI Design Guidelines for Apps
Page 20
An organizational shift occurred
Page 23
Benefits of the Transition
Page 26
Find a framework
Step 1
Page 28
Student AffairsIT
Academic AffairsIT
Housing & DiningIT
LibrariesIT
Admin Computing
Academic Computing
Student AffairsIT
Framework that required data feeds had downsides
Page 29
Student AffairsIT
Academic AffairsIT
Housing & DiningIT
LibrariesIT
Admin Computing
Academic Computing
Student AffairsIT
Page 31
We launched m.ucsd.edu
Page 32
What about ouriPad App?
Page 33
Replace the App
Step 2
Page 34
iOS App: powered by m.ucsd.edu
Page 35
m.ucsd.edu iPhone App
Page 37
Android App: powered by m.ucsd.edu
Page 40
What about all the CMS content?
Page 41
Piloted with the Libraries
Page 42
Courtesy: Brad Frost
Page 43
We weren’t the only ones trying to solve this problem
Tantek Celik, Dan Cedarholm, Jeremy Keith, Eric Meyer, Ethan Marcotte, Jeffrey Zeldman, Nicole Sullivan, Wendy Chisolm
Page 44
One of them wrote and article that started a buzz…
Page 45
The dude even wrote a book about it!
Page 47
.HTML(structure)
.CSS(layout)
The solution is based off existing web technologies
Page 48
CSS3@media
+
Fluid Layouts Media Queries
Page 49
Fluid images & media
Page 50
One website that works on all devices
Page 51
One website that works on all devices
Page 53
What about the Mobile Web Framework?
Page 54
You want me to make THIS responsive??
Page 56
Responsive design for Websites & Apps
Mobile Framework when RWD won’t work
Page 58
Works for apps too
Page 61
Make sure your design looks good in all resolutions
Add breakpoints when the design starts to break down
Page 63
Device resolutions to access ucsd.edu in one month
Page 64
fluid layouts using percentages
Responsive Design
fixed width layouts targeted for specific devices
Adaptive Design
Page 66
Be ready to iterate
Adjust development cycles to be agile
Page 67
Does it take more time?
Yes. It will increase the length of a project by 32.6345%
Page 68
There is no more “fold”
Work with content owners to pair down content
Page 69
Test on real devices
Ask different teams to pitch in and help test
Page 71
Images
Devices with smaller resolutions still need to download the full image
Page 72
RESSResponsive Design + Server Side Components
Offload some of the work to the server…
Page 73
The Idea is to:Deliver certain components based on the device, rather than loading all at once for every device.
RWD .js .jpg .php
Page 76
1. Use a Responsive Web Design framework as the primary way to deliver websites & web apps
2. Use a Mobile Framework to augment when responsive design won’t work
3. Deliver the frameworks through a central host and allow other IT units to leverage the capabilities
4. Finally…
Page 78
ResourcesRESPONSIVE WEB DESIGN
By Ethan Marcotte alistapart.com mediaqueri.es
FRAMEWORKS Foundation3 Twitter BootstrapHTML5 Boilerplate