Comment 23 for bug 885320
Revision history for this message
| Lionel Dricot (ploum-deactivatedaccount) wrote Re: GTG needs a GTK3 port and a UI redesign | #23 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
a60fb26
(Get the code!)
vovkkk > to be able to enter tasks with subtasks and subsubtasks in GTG was one of our first idea. And it was even implemented.
Then, we realized that it simply doesn't work because people write down tasks in the order they will make it:
- take out the old lightbulb
- buy a similar lightbulb
- replace the lightbulb.
The structure should be the following:
1) Replacing the lightbulb
2) Buying lightbulb
3) Taking out the old lightbulb.
Do you see the point?
We had no choice but to remove this feature completely before the first release because even us were confused!
Reda > Thanks for the mockups. What I want to say is that "doing mockups" is not just "trying to draw an interface using your intuition". There's a whole process behind it. If you don't start by identifying the needs and the workflows, your mockups might be worthless anyway.
The workview is described in the first time tasks you have when starting GTG for the first time. Approximately 50% of GTG users don't use it. That's not a problem because the feature is not in your way if you don't use it. The other half cannot live without that feature, which is one of the key selling point of GTG.
That's where UX becomes hard. You cannot judge from your experience. You have to take into account the global audience. And your experience itself is not even relevant at all (not more than mine or Izidor's one).