However,
with the release of iPhone and iPod touch, those assumptions are now invalid. Web designers are
thus forced to rethink their reliance on a technology that they had become dependent upon. Figures 8 - 1
Figure 8-1: Flash-based site that attracts desktop users . . .
Chapter 8: Enabling and Optimizing Web Sites for iPhone and iPod touch
181
Figure 8-2: . . . leaves iPhone/iPod touch users out
in the cold.
Therefore, if you plan on using Flash for an interactive portion of a page, then you should plan to
degrade gracefully to a static graphic or alternative content. At a minimum, you should at least do what
Adobe does (see Figure 8 - 3 ) in placing a disclaimer over Flash content. It ??™ s not ideal, but it is better than
the Lego block. Or, if you have a Flash - driven site (such as the one shown in Figure 8 - 1 ), then you should
consider an alternative HTML site or, if warranted, even an iPhone/iPod touch ??“ specific site.
In order to detect Flash support, one solution is to use SWFObject, an open source JavaScript library that
is used for detecting and embedding Flash content (available at blog.deconcept.com/swfobject ).
SWFObject is not iPhone/iPod ??“ touch specific, but encapsulates the Flash Player detection logic, making
it easy for you to degrade gracefully for Mobile Safari.
Pages:
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213