Timeline for Should task based interfaces be implemented all-the-way or partially where it makes sense?
Current License: CC BY-SA 4.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 28, 2020 at 1:13 | vote | accept | tlt | ||
| Oct 28, 2020 at 1:10 | comment | added | Nicolas | There is prob not a universal answer to this. What matters is what the user performs the best at balanced with your dev budget. I would say test it with your users, or talk to them at a minimum, show them all versions and ask them to perform a few of the usual tasks. | |
| Oct 28, 2020 at 0:45 | comment | added | tlt | maybe rephrased: if we decide to go with task based UI - should we at least try to have it everywhere or go for it just where its completely obvious its a good choice? are there any general "guidelines" like that? | |
| Oct 28, 2020 at 0:44 | comment | added | tlt | so, lets say like this... since this is not some form-editing app and although there are different roles, all of them do have some special, partial things to do. there is practically no case for creating/updating whole entities (they are imported initially without users interaction). still, CRUD could also be form with 5 fields 2 of which are read only and 3 of which are editable. so i guess question is also: should we always strive for task based interface whenever possible or should we consider it fully free choice without any special bias to it? | |
| Oct 27, 2020 at 23:49 | history | answered | Nicolas | CC BY-SA 4.0 |