Taskfox/Goals

	THIS PAGE IS A WORKING DRAFT
	The page may be difficult to navigate, and some information on its subject might be incomplete and/or evolving rapidly. If you have any questions or ideas, please add them as a new topic on the discussion page.

Goals

Work with existing workflows, not against them

Existing workflows should not be broken, interrupted, or compromised in any other way.

A large part of perceived software bloat comes from piling on new features without a unified vision — each disjoint, with their own way of doing things, and own way to invoke them. The more we can place time-saving designs in the path of current work flows, the smarter, quicker, and lighter the software feels. Done well, the feature doesn’t even really feel like a feature, just a lending hand: “of course it was supposed to work that way”, says the user.

A corollary, however, is that we can’t block the old work flow by trying to “help”. That would be rude.

Tasks, rather than individual steps

At the moment, many common tasks (such as emailing a snippet of text to a friend) require you to repeat the same series of discrete steps each time. Give that these steps are already known, this workflow can be streamlined into a single step.

Non-goals

Create a platform

While Ubiquity is a platform for quick and easy extension and command development, Taskfox is not. As such, Taskfox will not be:

• Be extendable through command feeds
• Be extendable through experimental UIs