> For the complete documentation index, see [llms.txt](https://docs.onside.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.onside.io/sdk/customization/appearance.md).

# Appearance & Theming

Apply a consistent global theme to all screens presented by OnsideKit using OnsideAppearance.

`OnsideAppearance` sets global styling for every screen OnsideKit presents. Access the shared instance via `Onside.appearance()`.

## Set the global theme

```swift
@MainActor func setThemeMode(_ themeMode: OnsideUIThemeMode?)
```

```swift
Onside.appearance().setThemeMode(.dark)
```

`OnsideUIThemeMode`:

* `.auto` — follow the user's system appearance (Light/Dark)
* `.light` — force light
* `.dark` — force dark
* `nil` — reset the theme setting (does not affect already-presented UI)

The best place to set this is at launch:

```swift
func application(
    _ application: UIApplication,
    didFinishLaunchingWithOptions launchOptions: [UIApplication.LaunchOptionsKey: Any]?
) -> Bool {
    Onside.initialize()
    Onside.appearance().setThemeMode(.dark)   // force dark for all OnsideKit screens
    return true
}
```

## Theme resolution

When OnsideKit presents a screen, the theme is resolved in this order:

1. A per-screen override from [`OnsideDelegate.onside(uiThemeOverrideForScreen:)`](/sdk/customization/delegate.md#per-screen-theme-override), if provided.
2. The global theme set here via `setThemeMode(_:)`.
3. The system appearance.

{% hint style="info" %}
Theme mode is currently the only globally configurable appearance setting.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.onside.io/sdk/customization/appearance.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.