Thanks for your help. You make a lot of good points, and the more I thought about it last night, the more I was leaning towards an in-browser app.
I can do all of the CSS/html/PHP/mySQL code myself. Where it looks like I may run into some issues with is the AJAX. I don't have much experience with it. It's going to be interesting to see if I can handle the "no page refresh" updates as well as the instant "add to faves" and "remove from results". One other thing I will look for examples of is reordering/adding/removing
Main Topics
Browse All Topics





by: tomaugerdotcomPosted on 2009-04-03 at 06:35:15ID: 24059738
There is no _issue_ based on what you have listed. Having said that, it seems to me that there's not necessarily a great case for AIR here, vs. thin client / in-browser app. My reasoning is that it seems you require a persistent internet connection for this to work at all. In light of that, the user expectation is that a standalone application should be that - standalone. Whereas if they're doing something in a web browser, the user expectation is that they need a connection.
Now if it's purely an aesthetic / chrome issue, then I can see wanting the benefit of a nicely-skinned AIR app. Just be sure that you're polling the connection to the server and are prepared to pop up an alert to the user if the connection is lost or sync is not kept up. That way they'll know why the application has stopped responding / functioning as expected.
Sounds like a cool project. You already have a dev team for this one?
T