Answer the question
In order to leave comments, you need to log in
What is the best way to present nesting in an interface with easy navigation?
I am writing a simple task tracker in the form of a website.
Everything is standard in it in terms of entities: tasks , notes , files , etc. are combined into projects . I would like some advice on how best to design the interface for easy navigation through these entities (especially in terms of switching between projects).
Here are the options that immediately come to mind:
1st option
2nd option
Which option is better? Maybe there are more ideas?
Answer the question
In order to leave comments, you need to log in
I do not consider myself a specialist in the field of usability, but the second option is better IMHO.
In the first one, you immediately feel that something is not right.
The duplication of Tasks and Notes creates a modality. Always keep in mind what I choose - general tasks or just the current project? The first option is better.
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question