For example a desktop app may ask for 'user_id:'
where as the web app would ask for 'Your email address:'.
I'm sorry but I don't quite agree with the above. In the desktop apps that I have written if I wanted their email address I would ask for it.
As to documentation in place. I can see your view point in one respect as we typically allow for instructions above each form (as an example) that explain the processes or requirements of the following immediate action. However, that does not really help to reinforce the process as a whole nor does it really ensure the user is aware of what is happening (which is in reference to your last point).
All that it does is ensure that *at that point* in the application the user *is somehow aware* of the requirements of that *particular form*. Of course whether its the right form for what they want to do is down to the application and the user ;).
I guess ultimately it boils down to how much confidence you have in your user base and how complex the application is (which is in itself a moving target with shifting user requirements).
Thnx - SP
Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
Want more info? How to link or
or How to display code and escape characters
are good places to start.