Quote:
Originally Posted by Brian
Action groups are one of the topics we plan to revisit in future versions of the application, but IMO, naming actions unambiguously is just a good habit to cultivate in general.
|
Thanks. It could just be a preference to show a bit of text of the parent action if it's shown out of context (like a breadcrumb trail).
It saves a lot of time to have quick, shortly-worded actions IMO.
Compare:
- Update Omnifocus context mode
--- Write use case
--- Design wireframe
--- Early usability testing
--- Mock-up
--- Prototype
--- Usability testing
--- Final design
When you have to repeat similar steps as sub-actions to a similar task, the sub-actions are easy to copy and paste. This also makes it harder to scan.
The alternative:
- Update Omnifocus context mode
--- Context mode redesign: Write use case
--- Context mode redesign: Design wireframe
--- Context mode redesign: Early usability testing
--- Context mode redesign: Mock-up
--- Context mode redesign: Prototype
--- Context mode redesign: Usability testing
--- Context mode redesign: Final design
Phil