HTML and CSS Reference
In-Depth Information
Figure 6-21. The presenter view
Smaller Screen Layouts (and Why You're Not Designing
Them Here)
We spent a lot of time in the last chapter discussing the benefits of a mobile-friendly web app versus a suite of native
apps. So why aren't you designing the mobile version now?
The main reason is that mobile design is, by its very nature, too fluid to really lend itself to traditional design.
It requires a little more of a hands-on, try-it-and-see approach that would take way too long in Photoshop. 6
Due to the simplicity of this particular layout, another reason not to do mobile-specific layouts is for the purposes
of time. If it's easy to make the changes in CSS, that time is better spent coding. No need to double the effort required.
Summary
In this chapter, you applied all the planning from the previous chapters and created a design for the app. Because
you're organized and you thought ahead, your PSD contains styles and fonts that can be replicated very closely
using CSS.
In the next chapter—at long last—you will finally start coding this app. More specifically, you'll be building the
front end, including the advanced CSS that will make this design adapt to any screen size.
6 It would appear that Adobe knows this as well because they're working on a new tool to address the issue:
http://html.adobe.com/edge/reflow/ .
 
Search WWH ::




Custom Search