At the application level, we provide explicit representation of these tasks via Intents, i.e., developers write Intents to dynamically configure and invoke the tasks.
And good design needs an in-depth understanding of users' tasks, motivations, intents, strategies, and detailed steps, as well as an overall grasp of how they go through their days, what technology they depend on, who is important to them, and their self-image.
Thus, storyboards are guided by and checked against the consolidated sequences for tasks and intents that need to be supported.
But in task completion, user-intent is directly explained by the user – because the user can state their goals directly, and refine their intent in a conversation.
This is because task completion uncovers consumer intent more explicitly than search.
Further, the selected task is configured with Intent's configuration parameters and a payload, and finally executed.
A: The focus we have is not as much on non-Google content – it's more on query intent and task completion.
Whether it is a quiet moment just before you embark on something new, or the times when you need a little more energy to get you through the day, it is a great way of giving the task at hand the intent and focus it deserves.
"Sharpshooter" (1863) finds a Union sniper athletically perched in a tree and intent on his task.
