I am confused, what are you taking about with "trying to fool the app store"
There are actually three types of web applications 1) websites optimized for viewing on the iphone 2) hybrid applications are those that are essentially web applications that are wrapped in a c++ wrapper execute as part of webkit. 3) Web applications that are very similar to non iphone applications that are heavy in ajax, are very server managed and are either subject to frequent maintenance or are very dependent on web based resources. The fat client approach if you will. Let me describe just one of our applications in development that will we hope eventually fit into (2) above right now is would best be described as (3). But there is no fooling of the app store, this is not a native application. Artshow is a simple image browser, somewhere on your server Java/ Tomcat you place a folder of images of various resolution. The java based servlet reads this folder formats it as a json feed and passes it to the webapplication. The Artshow Proof of concept is an icefaces (www.icefaces.com) custom component . Components use imbedded javascript in this context artshow's javascript was created using dashcode. Artshow was a simple proof of concept , our next attempt is something called tagalong, which will eventually be hybrid application. there is a very good book on Hybrid iphone applications. "Developing Iphone hybrid applications" available from Sams publshing. To envision tagalong, imagine this use case, which cannot be accomplished with a native application. imagine a campus community of a moderate size art college. a single subnet supports the campus network, On the wifi network are an unspecified number of servers. The servers make use of various media distribution protocols, upnp, bonjor etc. All servers are java based and use zero config (bonjour) to publish their Ip's. Servers come and go frequently from the network. At a given time there could be as many as 3000 concurrent users browsing the art works. The application itself acts a bridge between these servers, it discovers the servers via bonjor , the dsn-sd (bonjoir) record has both the server address and info including name. These are sorted into lists and streamed to the iphone web client. The iphone user merely needs to sign on to the bridge, which sets up a continuos long pooling connection between client and server and select a server from the list to see the content. http://web.me.com/cannonwc/Site_3/Photos.html#6 The backend keeps track of the number of concurrent users and allocates resources as needed to support the load. The above completes the non native/non hybrid application, that can be used on or off the subnet of the campus. The hybrid app brings the above webapp into a webkit wrapper on the iphone. The hybrid provides several types of local functionality. 1) additional images can be added from the phone and sent to the server 2) The discovery service can show bonjor locations local to the user. 3) the built in GPS of the phone can be accessed to show the locations of the real galleries on campus, and to geo tag the photos sent to the server. Later streaming video can be added as the app matures. I hope the above description of our application shows a couple things. 1) that there is a place for all 4 types of applications, websites, fat clients, hybrids and native applications. 2) that there are a lot of choices for ide's and languages in developing iphone applications. 3) that most of the relentless ranting in this group has no ground. Check out all our projects at www.mooncatventures.com --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
