> For the complete documentation index, see [llms.txt](https://docs.buildnatively.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.buildnatively.com/natively-platform/appearance/style.md).

# Style

Some bellows parameters can be updated with SDK later (check [Control Style & Colors](/guides/integration/control-style-and-colors.md) section)

[#app-background-color](#app-background-color "mention")

[#loader-color](#loader-color "mention")

[Style](/natively-platform/appearance/style.md#swipe-navigation)

[#pull-to-refresh](#pull-to-refresh "mention")

[#status-bar-style](#status-bar-style "mention")

[#safe-area](#safe-area "mention")

##

## Colors

### App Background Color

The top background (It displays only on iOS devices with notch)

If your page background is transparent, it will be the page's background.

![Top bar background (If iPhone with notch)](/files/YexLHOL7abzxGejH1MQ0)

### Loader Color

The color of a loader on the top (This loader will be displayed only while the page is loading)

![](/files/lhUSAo2g0rATtYKZhGyH)

## Device

### Swipe Navigation

Users can navigate between pages with a swipe gesture

![](/files/GVhmiYmyTblePZ2EdUZE)

### Pull To Refresh

Drag to the bottom to refresh the page

![](/files/CYlAZB0TVnGEpD1Tn8gw)

### Status Bar Style

In iOS: Status bar color, can be "Dark", "Light", or None(Hidden)

![](/files/Qb14Y0Gb2rD4aWiZhZgx)

In Android: "Dark" or "Light"

<figure><img src="/files/wySxBpXhTBR4ekQ0oljq" alt=""><figcaption><p>DARK</p></figcaption></figure>

<figure><img src="/files/FJ4WCLp8SuH81ROwFzyE" alt=""><figcaption><p>LIGHT</p></figcaption></figure>

### Safe Area <a href="#safe-area" id="safe-area"></a>

Safe Area - it's a space on the top of the app, that can be Enabled/Disabled.

{% hint style="info" %}
If it's Enabled, the background can be controlled by [App Background Color](#app-background-color)
{% endhint %}

<figure><img src="/files/iqewm5fqMreJAVgRzOXh" alt=""><figcaption><p>Disabled</p></figcaption></figure>

<figure><img src="/files/rqGo0530lifg3jB7wWVj" alt=""><figcaption><p>Enabled</p></figcaption></figure>

### Resize Viewport

Enabling this option adjusts the viewport, allowing users to scroll and access focused input fields that are obscured by the keyboard.

### Bottom Overlay

Enables Android navigation bar.

### Background Audio

Enable this feature if your app requires background audio playback.

{% hint style="warning" %}
If you enable this feature but your app doesn't require it for any functionality, your app may be rejected by Apple for: "The app declares support for audio in the UIBackgroundModes key in your Info.plist but we are unable to locate any features that require persistent audio". In such a case, you should disable the feature, save your changes, rebuild your app, and resubmit it for review.
{% endhint %}

### Wake Lock

Prevent your app from automatically locking the screen.&#x20;

{% hint style="info" %}
If it's Enabled, the feature can be controlled by [Wake Lock](https://docs.buildnatively.com/guides/integration/control-style-and-colors)
{% 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 dynamically by asking a question.

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

```
GET https://docs.buildnatively.com/natively-platform/appearance/style.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.