# User Workflow

Visible design is a large part of the user experience, but so is the user's workflow, or how they interact with an app. In this section, we cover a few important steps of a typical workflow:

* [First Launch Experience](https://docs.elementary.io/hig/user-workflow/first-launch-experience): What the user sees the first time they use your app
* [Normal Launch](https://docs.elementary.io/hig/user-workflow/normal-launch): What happens when opening your app on a day-to-day basis
* [Always Provide an Undo](https://docs.elementary.io/hig/user-workflow/always-provide-an-undo): Help users be faster and more confident
* [Always Saved](https://docs.elementary.io/hig/user-workflow/always-saved): Bringing the desktop in line with modern expectations
* [Closing](https://docs.elementary.io/hig/user-workflow/closing): What happens when closing your app
* [Background Tasks](https://docs.elementary.io/hig/user-workflow/background-tasks): How your app manages to do things invisibly in the background


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.elementary.io/hig/user-workflow.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
