> For the complete documentation index, see [llms.txt](https://opusecom.gitbook.io/opus-mobile-builder/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://opusecom.gitbook.io/opus-mobile-builder/design-customize/publish-your-docs.md).

# Branding Configuration

### Branding Settings

The Branding section allows you to configure key visual elements that define the identity of your mobile app. These settings help ensure your app reflects your brand consistently across all screens.

Branding configuration typically includes:

* Typography
* Splash Screen

***

### Typography

Typography controls how text appears throughout your mobile app. Setting consistent typography helps improve readability and create a professional user experience.

#### What You Can Configure

You can typically customize the following:

* Primary font – the main font used across the app
* Heading styles – fonts used for titles and section headers
* Font sizes – adjust text hierarchy across headings and body text
* Font weight – control boldness of text elements

These settings apply globally across your app to maintain visual consistency.

#### How to Configure Typography

1. Go to App Design
2. Open Branding
3. Select Typography
4. Choose the font family for your app
5. Adjust heading and body text settings
6. Save your changes

![](/files/i8x3GoklLdnQRRgh1M8F)

#### Best Practices

* Use one primary font family for a consistent design.
* Ensure text contrast is strong enough against background colors.
* Avoid using too many font weights to keep the UI clean.
* Test readability on smaller mobile screens.

***

### Splash Screen

The Splash Screen is the first screen users see when opening your mobile app. It usually displays your brand identity while the app loads.

A well-designed splash screen creates a strong first impression and reinforces brand recognition.

#### What You Can Customize

You can upload a splash screen image that will be displayed when the app launches.

#### Recommended Design

For the best experience:

* Use a high-resolution splash screen image
* Use PNG or SVG format for better quality
* Ensure transparent backgrounds when needed
* Keep the design clean and centered
* Avoid placing too many elements on the splash screen
* Avoid small or pixelated images
* Ensure the design matches your brand identity

#### How to Configure Splash Screen

1. Navigate to App Design
2. Open Branding
3. Select Splash Screen
4. Upload your brand logo
5. Save the configuration

![](/files/5Jj9ec7gI7QnTXXHiCki)

***

**Preview Your Branding**

After updating your branding settings:

* **Open Ego Live Preview**&#x20;
* **Review how your branding appears in the app**
* **Check typography readability**
* **Verify splash screen appearance**
* **Confirm that brand elements look consistent across the app**

This helps ensure your branding is displayed correctly and consistently before submitting your app.

<br>


---

# 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://opusecom.gitbook.io/opus-mobile-builder/design-customize/publish-your-docs.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.
