Andy Fuchs wrote:
> Due to the amount of 1.0.2 versions of the iPhone out here, I'd suggest
> lowering this point, because the current implementation works across
> versions and a change could break core functionality.
>
>
snip
> While adding support to Safari 3 it also would be nice to have the UI
> running well on Firefox (and *maybe* Safari 2 - not sure).
Good points, Andy. We need to define what platforms/versions iUI
supports. I'm not sure if we can use terminology from Apple's
guidelines, but there might be three or four categories of operation:
1) Fully supported, optimal
* Mobile Safari on iPhone (1.0.2 or later?) and iPod Touch
* Other compatible devices and browsers?
2) Supported with some caveats
* Desktop Safari (2+ or 3+?)
* Firefox?
3) Catch-as-catch-can
(Pages might be viewable but with questionable usefulness/appearance)
4) Broken
(Pages don't work at all? Users are redirected to an error page or
a main page for a desktop site?)
1 & 2 could perhaps be combined, so could 3 & 4. I don't really
understand all the issues involved in browser support, nor do I know
what developers and end-users would really want here, so the above is a
strawman to get discussion going.
Apple has some terminology for "levels" of iPhone support (like
supported, compatible, optimal -- or some such). I can't seem to find
it right now. Does anyone have a link?
Apple's terminology is used to distinguish between a desktop site, a
desktop site that works well on an iPhone, an iPhone-optimized site,
etc. In our case, we want to describe how an iPhone-optimized site
degrades on non-iPhone browsers.
-- Sean
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
