[spydre100]

Slick was perhaps the wrong word. I think that it is agreed that the use of ajax (in the right way) makes app more usable slick. I think facebook is a good example of this. Their ajax implementations make for a more usable UI.

I think that on that note the simple mobile implementation again refering to facebook can be done in a simplistic manner but with good usability.After-all it is agreed that simple is good. This it can be done very quickly. It's also a good way to test the "useability" of a concept.

Since we are low on resource and un-funded would it be a bad decision for us to tackle the mobile app in this way, quickly. Start testing the useabilty of our app with a handful of users while we move on to a more advance slick as i put it ajax'd version for more advance browser clients ???

[kls]

My personal belief, that has been reinforced by my experiences, is that one should take the path that leads to a revenue the fastest without damaging the brand. But it does take a lot to damage a software brand. A lot of people talk about PG's MVP I have never read or heard the exact conversation about it by PG but from peripheral conversation that I have seen about it, I looks to be a similar concept. Point is, don't target the largest market, target the market you can get to first and build the minimum feature set that will capture it. It buys you time, even if you have to scrap and rewrite the whole thing for 2.0 you should build it as rapidly as possible with the minimum feature set required.