Software/Interface design
Software/Interface design
Out of context: Reply #3
- Started
- Last post
- 6 Responses
- g3kk0k1d0
I would personally recommend starting with the main tasks and building outward, forget the nav position etc, work with the main task and fulfill only what the task needs to complete nothing more
understand the principle tasks of the software design, that is the key.
dont start with the content but with a blank/empty state where the task has just been initialised and all the input is empty.
the empty state is the first thing the user will see, that will be the first impression from the users viewpoint, its where the app is deteremined
when you dealing with multiple features, think to yourself - "do i really need that?" if you don't just kill it.