Datasheet
CHAPTER ONE FUTUREPROOF SURVIVAL TECHNIQUES
17
A better approach is to examine the symptoms, make a diagnosis, and nd suitable solu-
tions to treat the condition. It isn’t the brand or model that makes a device; the compo-
nents make the device. e inside of an iPhone and the code it supports (such as HTML)
di er signi cantly from what you nd in a Nokia 6610i (which supports only WML, as
shown in Figure 1-4). e issue boils down to two independently built renderers doing
what they can.
Figure 1-4: When compared to today’s rich and engaging HTML and CSS, WML is a real ugly
character.
Ultimately, the choice to keep up with the trends or retain support for only a select few of
your audience’s situations is entirely up to you. It may be impractical to produce a site that
is so exible that it supports every type of product and situation without issue, and if you
know what your audience requires, there’s no need to go over the top, covering all possible
bases. However, unless you have a good reason to do otherwise, ensuring that your site
caters to as many situations as you can eliminates the need to patch your site’s code in the
future.
e browser wars proved that creating sites that depended on everything rendering in
one way was problematic. Designers have since adopted more stringent measures for test-
ing work ows. Currently, designers are struggling with the fact that devices and plat-
forms force you to rethink how you present and organize content. In the future, perhaps
your next tussle will be over dependency on frameworks, the continued support for dep-
recated code, or something else entirely. I do enjoy a good mystery—don’t you?
04_9781119978770-ch01.indd 1704_9781119978770-ch01.indd 17 10/25/11 1:08 PM10/25/11 1:08 PM