Your app either looks and performs like a series of web pages, which means it has hyperlinks or it looks and performs like an application and doesn’t.

Input field history is implemented by the browser, but because I don’t use that feature in my day-to-day web usage, I can’t really comment on how Web 2.0 techniques would affect that feature. My impression was that form auto-fill and input history were based on the “name” attribute of the field, which shouldn’t be any different in a Web 1.0 or 2.0 context. I’ll have to try an example to see what you’re talking about.

Another web 1.0 UI pattern I was missing in web 2.0 apps just recently:
- “Browser form field input history”; that is: Values, which have been typed into a form field before, are NOT suggested later on … This “input value suggest pattern” – e.g. based on former input values – is supported for plain old HTML forms in all browsers; and for a good reason: One just does not want to type in already typed in values – numbers, strings, dates, etc. – over and over again …

IMO deep linkability as well as form field input history are very important patterns for usable UIs ! My questions are now:
- Could there be even more important web 1.0 UI patterns which have been overlooked in web 2.0 UIs ?
- Does Appcelerator support “Browser form field input history” ?
- What about those patterns in widgets leveraged by Appcelerator ?