# Build your own UI
URL: https://docs.awellhealth.com/docs/embed-and-host/build-your-own-ui

> For the complete documentation index, see [llms.txt](https://docs.awellhealth.com/llms.txt).



A custom interface on top of the Orchestration API gives full control of every pixel and interaction,
and means owning every edge case.

Before choosing it, be clear about what the other options already handle:

* **[Hosted Pages](/docs/embed-and-host/overview-hosted-pages)** already handles accessibility,
  internationalization, responsive layout, keyboard navigation and form auto-save, all of which take
  real work to rebuild well.
* **[Navi](/docs/embed-and-host/what-is-navi)** renders activities inside the host product, with the
  organization's branding, while Awell maintains the activity rendering and its edge cases.

Build a custom UI for something genuinely different: an interaction model neither supports, or a
surface such as a kiosk or a native component that has to be first-party.

## Everything a UI needs is in the Orchestration API [#everything-a-ui-needs-is-in-the-orchestration-api]

The API covers reading pending activities, submitting form responses and completing activities. See
[the API reference](/api-reference).

The [activity model and lifecycle](/docs/embed-and-host/activity-model-and-lifecycle) is worth reading
even without Navi, because it describes the states a custom UI has to handle.

## Next steps [#next-steps]

**Next:** [What is Navi?](/docs/embed-and-host/what-is-navi), often the middle ground between a custom
UI and Hosted Pages.