Hey Gordon, I would first question why your isolating only those running mobile safari on iPhone as candidates for the alternate content. Obviously presenting flash content is not an option for iPhone visitors BUT why limit the alternate content to just those folks? If it we're me, I would utilize SWFObject:
http://blog.deconcept.com/swfobject/ You could easily detect the player and present the appropriate content accordingly regardless if they are on a desktop or mobile. The other HUGE advantage not mentioned in this dialog is SEO. Because SWFObject injects the content based on the presence of the player, when your site is indexed by search engines, they will see and crawl the non- flash based content. If for one reason or the other, you'd still like to isolate iPhone users I'd still recommend using SWFObject and just setup a condition to handle those specifically on an iPhone after they've come up negative for the player. -m --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "iPhoneWebDev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/iphonewebdev?hl=en -~----------~----~----~----~------~----~------~--~---
