Note that there are some explanatory texts on larger screens.

plurals
  1. POAvailable iPhone Web Application JavaScript UI Library/Frameworks
    primarykey
    data
    text
    <p>I'm starting a web application that will target Mobile Safari on iPhone/iPod Touch. I'm evaluating the available client-side JavaScript/CSS libraries/frameworks that are currently out there.</p> <p>These are the ones I'm currenlty aware of:</p> <ul> <li><a href="http://code.google.com/p/iui/" rel="nofollow noreferrer" title="iUI">iUI</a></li> <li><a href="http://code.google.com/p/ciui-dev" rel="nofollow noreferrer">CiUI</a></li> <li><a href="http://code.google.com/p/iphone-universal/" rel="nofollow noreferrer">UiUIKit</a></li> <li><a href="http://webapp.net.free.fr/" rel="nofollow noreferrer">WebApp.Net</a></li> <li><a href="http://snippetspace.com/projects/iwebkit/" rel="nofollow noreferrer">iWebKit</a></li> <li><a href="http://developer.apple.com/documentation/AppleApplications/Conceptual/Dashcode_UserGuide/Contents/Resources/en.lproj/Introduction/chapter_1_section_1.html" rel="nofollow noreferrer">Apple's Dashcode Application</a> - not really a standalone library/framework, but it provides/generates JavaScript, CSS, and images that conform to the native iPhone UI metaphors.</li> </ul> <p>Are there any others out there? I want to make sure I'm not missing any before I make a decision. I'm only looking for client-side JavaScript/CSS solutions and building one from scratch isn't an option because of time constraints. No server-side PHP, Ruby, Python, Java, etc. solutions.</p> <p>I am aware of the <a href="https://stackoverflow.com/questions/8756/iphone-web-applications-templates-frameworks">iPhone web applications, templates, frameworks?</a> question that was asked, but this only mentioned iUI and UiUIKit.</p> <p>Thank you</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload