3 ms·

This looks like an excellent library, the demo works nicely on my iPhone, but... I think that simulating native UI is a bad idea all around. If it looks like a

This looks like an excellent library, the demo works nicely on my iPhone, but... I think that simulating native UI is a bad idea all around. If it looks like a native app, acts like a native app, I expect it to do everything like a native app. This gets 90% of the way there, but due to the nature of the browser will never be 100%. I think you are better off with a unique look and feel that won't confuse users. You'll also spend less time developing it, as you won't struggle to get every little detail to match.

cakesy 17y ago
There is actually loads of sites out there, that duplicate the iphone functionality, when in mobile mode. There are other toolkits to make your web more iphone-like. It has its advantages and disadvantages. Most people don't even know what the different is between a web app and an iphone app, so I think it is a reasonably safe bet.
- njharman 17y ago
  > Most people don't even know what the different is between a web app and an iphone app Exactly! That is the problem. They don't know your web app is an iphone app. So, they get annoyed when it doesn't have all the functionality of an iphone app. They have higher bar of expectation that a webapp inherently can not reach. If it was obviously a "web page" then user expectations are much lower and they are likely to be impressed by what it can do. The key to success is not being good. It's being better than expected.