
everything will be in "modules"
so that its easy for mobile user to go to "sections" of workorder for what they need to work on
whereas bigger the screen, more "sections" can see at a time within reason, as still don't want to overwhelm the end user - better to have white space


Major idea:
 
R P B
Iv'e been trying to figure out what's the best way to determine what a user sees when they view a workorder.
Figured it out.

When first create a new workorder, by default shows the R for Service Required "tab" (tab is in quotations because not a real tab, just looks like that to the end user so less on the "page"
If the user wants to "jump" to entering P for Service Performed, they certainly can.
Same if the user wants to jump to just entering billables.

Now if a user views an existing workorder:

- role dependant
 - if that user role is Tech or Subcontractor and has not ever viewed that workorder before, than that user views the R section by default (so can see what the Required service is) 

 - cause the tech / subcontractor can enter labor etc "from" the required area.

if invoicer role, can go straight to Billables (unless billables has been disabled, but than if disabled, why is someone with a billables role?)







"weblication" instead of web application




http://www.webdesignerdepot.com/2009/02/7-interface-design-techniques-to-simplify-and-de-clutter-your-interfaces/

modal windows - not popups, but popups "on top" and behind is grayed/darker/obviously not in use, but user can stillsee


hover - controls only show when hover over (or tab to)
as in a list of workorders are returned. Don't need the menu options until actually hover over (edit, delete, report, change status, etc).

makes the windows cleaner



controls on demand: - This means you retain the advanced functionality for those users who need it, and at the same time simplify the interface for people who just need simple.


expanding form: - if have phone fields, Instead of having text fields for each , you could just have one, and then as the user fills them in, new ones are created underneath. Expanding the form in this way is a great way to save space and simplify your interface.



Labels inside input forms - instead of showing a label NEXT TO that text field, show the label as a pre-filled value INSIDE the text field.
(but what shows after? at all? or dependant if using mobile or not)

and when user clicks on a field to fill it in, still continue to show the "label" but just grayed out until they start entering (in case clicking was accidently and now don;'t know what the field was for).



icons instead of labels:  ONLY IF its incrediable obvious. I.e. weird icon that developer only knows what it means but to a layperson doesn't, can't do. I.e. can use a tag icon instead of the word Tag? 
if there is a danger of being ambiguous, you should play it safe and use a text label. 



Context based controls - By showing only a few relevant controls for a given task, your users can figure out what to do in much less time.
rather than the same menu regardless what the user is doing.

example in relation to ayanova: not sure

*********************

http://uxdesign.smashingmagazine.com/2009/01/19/12-useful-techniques-for-good-user-interface-design-in-web-applications/


eye notices movement - so refresh identifiying what's changed (i.e. highlight the changes))

still will need keyboard shortcuts


when all user's are scheduled, or when schedules overlap or are really busy, suggest to purchase more licenses/more staff?
i.e. You are really busy, hire more staff?


Green is successful
Yellow is warning
Red is fatal/major oops