# Applications

OnEarly is built in two layers. A shared foundation — the **substrate** — handles content, sharing, history and the parts of the app every feature needs. **Applications** add the screens and logic for a particular kind of work, such as ordering a pathology test.

## Terms

| Term | Meaning |
|---|---|
| **Substrate** | The shared foundation. In the backend: the content model (types, instances, permissions, history), notifications and APIs. In the app: navigation, sign-in, shared building blocks, a generic way to display any content, and views. |
| **Application** | Custom screens and logic for one or more content types, such as pathology ordering. |
| **Content type** and **instance** | A content type is a schema, stored as content. An instance is one record of it. See [Health Network](content-graph.md). |
| **Surface** | A size at which content is shown: **card** or **page**. |
| **Mode** | What you are doing with content on a surface: **view**, **edit** or **create**. |
| **View** | A substrate layout across many instances: a table or a list. |
| **Native** and **off-platform** | A native application runs inside OnEarly. An off-platform application is a separate product that uses the OnEarly API. |
| **First party** and **third party** | Who writes and runs the code: OnEarly, or someone else. |
| **Actor** | Anyone or anything that can own content, be given access to it, or make a change. See [People & Groups](actors.md#five-kinds-of-actor) for the five kinds. |

## How the layers fit

Applications depend on the substrate. The substrate never depends on an application, so any content still displays and shares correctly even where no application provides custom screens for it.

Diagram: [How the layers fit](https://docs.onearly.com/diagrams/core-model-applications.html)

## Applications today

| | First party (OnEarly) | Third party |
|---|---|---|
| **Native** | Pathology ordering, radiology requests, threads, scheduling, payment receipts | Not planned yet |
| **Off-platform** | Separate OnEarly products with their own app and backend. People sign in with OAuth; the backend calls the OnEarly API with a [group API key](/api/authentication#group-api-keys). | Outside apps you allow to use your account, such as AI assistants using OnEarly's MCP tools. See [Connected apps](../features/connectors-and-connected-apps.md#connected-apps). |

Native applications are built directly into OnEarly. Each offers its own operations, such as the steps of a request. A separate OnEarly product acts as its group, so it sees only content shared with that group.

You can revoke an outside app you have allowed under **Account → Connected apps**, one app at a time. OnEarly's own apps and products can't be revoked there.

## Surfaces and modes

Each surface can be shown in each mode. Where an application provides no screen for a surface, the substrate's generic display is used.

| Surface | Shown as | Typical place |
|---|---|---|
| **Card** | A summary | Lists, search results, conversations |
| **Page** | The full view | When you open the content |

| Mode | Purpose |
|---|---|
| **View** | Read the content. |
| **Edit** | Change content that exists. |
| **Create** | Make a new instance. |

Content also appears as a list row or inside a conversation.

:::roadmap
[Pills, cards and pages](../roadmap/exploring.md#pills-cards-and-pages)
:::

## Views

Views are provided by the substrate and work for any content type. You can save a view of your own content, or of a group's.

Views display as a **table** or a **list**. See [Views](../features/views.md).

:::roadmap
[Calendar view](../roadmap/exploring.md#calendar-view)
:::

## What we're working on

:::roadmap
- [Applications on a shared platform](../roadmap/exploring.md#applications-on-a-shared-platform)
- [Agent tools from application actions](../roadmap/exploring.md#agent-tools-from-application-actions)
- [Disconnect one app at a time](../roadmap/exploring.md#disconnect-one-app-at-a-time)
- [Content types that evolve safely](../roadmap/exploring.md#content-types-that-evolve-safely)
:::

Source: https://docs.onearly.com/core-model/applications/
