« Every app has a scary basement | Main | Dear phone OSes in 3rd place and beyond: Please accelerate your demise »

September 13, 2010


S. Irwin

In the first paragraph, do you mean "minimize" problems?

S. Irwin

Sorry, second paragraph.

Jan Miksovsky

S. Irwin: Right you are! Fixed. Thanks.

Mike W

Nice ideas. This topic is tangentially related to an issue I am dealing with in a project right now. I'm developing a data entry screen. The screen should give feedback to the user about the validity of the data, but I want the user to be able to save invalid data so that they can come back later to fix it. I want to avoid the situation in which a user enters a bunch of data and is then unable to save it. So the program will need a maintained a "valid" bit.


You make an interesting point about writing "SAME" in a field, but an electronic form can offer an even better option: a "Same" checkbox. That's common for billing/shipping addresses and should be used wherever else it's a likely desire.

My pet peeve is forms with rigid date and phone format requirements. A form should recognize all the common formats. Of course it might be necessary to disambiguate between mm/dd/yy and dd/mm/yy, but no software should demand a 4-digit year if there's only one conceivable century (e.g., when making travel plans).

The comments to this entry are closed.