Evaluation of the interface and design improvements

[mwittep]

Description

We want to deliver a functional product, but the usability should still be high. Hence, someone that has not yer used the interface as much as the client-side developers should evaluate and identify "design improvement". Some things that can be accounted:

• Text is always readable
• Buttons are always visible
• Grouping (aka distance between elements) is good enough to understand what belongs together, and what not.

• Acceptance

Please describe what is necessary for this ticket to count as resolved. You do not need to repeat the definition-of-done that your team has agreed on generally.

• [x] A person not related to the client-side developing can evaluate the interface and identify design improvements
• [ ] Such design improvements are implemented

Definition of Ready

If this issues has been discussed with the team and everybody agrees that it is implementable within one iteration, you can assign the label ready to it.

[AronWichtner]

I evaluated the interface and i noted the following points:

1. layout of main widget not centered
2. layout of main widget not adapted to screen size
3. project manager accessible even though no project was created
4. project does only not allow prediction if project name is empty -> user needs to be inforced to supply forward and backward wiggle, condition name, mastertable and gff-file (as far as i know we still need the gff and mastertable for the program to work)
5. visualization page not centered:
6. color of users screen has to be considered
7. go back button missing