Yes And thats why you see a lot of developers have a web version that covers the vast number of devices they want to support.
And a seperate native iphone version, because there are just some things you can do natively you can't do from the web. Performance for instance, if you need to do something special with javascript for instance jquery, in a native app you can keep that client side and feed it from something like touchJson. Of course in many cases there are native controls that handle the situation just as well. Watch the same thing happen with android (once they get a bigger user base) and Pre (once they get a decent sdk.). On Aug 6, 1:15 pm, Walter <[email protected]> wrote: > > I'm developping websites with some enhancement with JavaScript and > > wonder if it is possible to not make a separate version for the iphone > > but put the JavaScript together to work for both iphone AND desktop. I > > ran into some issues with jquery; some applications work, others not... > > but I'm far from knowing, why and what > > You can enable the javascript console on the iPhone to assist in > testing. All normal javascript should work, having said that, I have > run in to fairly serious issues with jQuery functionality failing (without > any warning in the documentation!) on as mainstream a browser > as Internet Explorer 7 for Windows. (Prototype/Scriptaculous, the > only other major Ajax library I'm familiar with, may be a better bet... > it seems a lot better documented than jQuery as their help pages > allow for community feedback) > > The bigger concern I would have with jQuery for mobile sites is its > size, plus the typical 'jquery.js', 'jquery-plugin1.js', 'jquery-plugin2.js' > pattern used by most jquery developers. > > Keeping the number of individual HTTP requests necessary to > render a page has even more significant impact on end-user > experience on mobile devices than it does on desktops. > > So the big picture... > > Given enough time, anything is possible. You can customise your > page layout based on screen resolution, device, phase of moon, > or any other factor. > > Unfortunately at this stage there are no more sophisticated toolkits > available than CSS and conservative use of javascript to ensure > maximum possible platform coverage, and if you leave it there you'll > fail to achieve coherently beautiful results on all devices. > > Proper display on many devices simply needs a lot of manual work. > > This is due to factors such as: > - some devices are touch screen (new N-series Nokias, iPhone, etc.) > whereas others (Desktop, older phones) are not, which has serious > impacts on site design and thus markup. > - touch screen devices vary significantly in resolution (not just in > terms of pixels, but in terms of physical DPI), which impacts > on site design (too many buttons too close together provide a > frustrating user experience) > - touch-sensor accuracy varies significantly, probably due to > differences in hardware, screen DPI, and click interpretation > algorithms (eg: iPhone beats N97 hands down in this area) > - any design making use of images (for buttons, etc.) will find that > their size must change on new devices due to massive DPI > differences > > Best of luck :) > > - Walter --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
