> For the complete documentation index, see [llms.txt](https://sonic-ai-works.gitbook.io/sonic-networks-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://sonic-ai-works.gitbook.io/sonic-networks-docs/documentation/application-and-website/mobile-applications.md).

# Mobile Applications

Canonical SONIC mobile product behavior for Expo/React Native, onboarding, five-destination navigation, Studio, Wallet and Settings.

SONIC mobile is a focused creator companion with native composition rather than a scaled-down desktop dashboard.

## Navigation

Production mobile navigation uses five destinations:

```
Home · Projects · Studio · Wallet · Settings
```

`Studio` is the centered raised SONIC control and remains one of the five destinations.

## Product flows

```
Start / Sign in
→ verification
→ goals / workspace
→ Home
→ Projects / Studio / Wallet / Settings
```

Home surfaces current projects, credits/usage and quick actions. Studio owns prompt/audio creation. Projects owns durable work. Wallet owns verified wallet/payment state. Settings owns account, security, appearance, provider preferences and billing.

## Composition

Mobile screens use single-column hierarchy, native bottom sheets, safe areas and 44px+ controls. Dense desktop inspectors move into sheets or dedicated screens.

## Themes

System / Light / Dark are supported through semantic tokens. SONIC red remains an accent/primary-action color; security and financial status maintain semantic colors.

## Product-truth boundary

Local PIN/biometrics do not replace server authentication. A wallet connection does not authorize a transaction. Cached/PWA state does not establish settlement, entitlement or private security state.

Developer implementation detail lives in **Developers → Frontend & Design System → Mobile UI · Expo & React Native**.


---

# 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://sonic-ai-works.gitbook.io/sonic-networks-docs/documentation/application-and-website/mobile-applications.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.