> For the complete documentation index, see [llms.txt](https://docs.blynk.io/en/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.blynk.io/en/commercial-use/business-plan-white-label-assets/branding-materials.md).
# Branding Materials
Icon, logo and other resources necessary for publication of Android/iOS applications in application stores
### App Name
Max length: 12 characters. We do not recommend to use a very long name as OS will truncate it.
### App Icons
Your app icon design is very important. Please follow [Apple](https://developer.apple.com/design/human-interface-guidelines/ios/icons-and-images/app-icon/) and [Google](https://developer.android.com/distribute/google-play/resources/icon-design-specifications) guidelines to design nice looking and recognizable icons.
Minimum requirements t
1. PNG or SVG
2. Size: 1024x1024px
For Android 2 layers are required. Transparency is allowed.
{% hint style="warning" %}
**Corner rounding is not allowed.** You need to provide images with no corner raiduses applied. Rounding is applied by an operating system of the smartphone. Different OS apply different rounding. So make sure that your icon content is not cropped with any radius
{% endhint %}
### Company Logo
You can add your company's logo or product logo to the login screen of your app. This will be the first thing your customers see when they create a new account or log in.
1. Format: .PNG
2. Size: 1440px wide or more
3. Transparency: Allowed
### App Branding
Console and mobile apps can be customized to reflect your company brand. Here is what can be customized:
* Dark or light theme
* Colors (you would need to provide your brand colors)
* 2 fonts (primary, secondary, numeric)
* Icons (where applicable)
* Custom images where applicable
* Automation cover images
Contact your Launch Support Engineer for details
---
# 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.blynk.io/en/commercial-use/business-plan-white-label-assets/branding-materials.md?ask=&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.