# Overview

> **Note**\
> This subsection describes how users interact with Aurex via the mobile application and what role it plays in daily usage.

The **Aurex mobile app** is designed for **quick access and daily account interaction** from mobile devices. It allows users to stay connected to their Aurex account without relying on constant desktop access.

The mobile application focuses on **visibility, control, and convenience**, rather than full platform configuration.

***

#### Primary use cases

The mobile app is primarily intended for:

* monitoring **wallet and card balances**,
* viewing **recent transactions and activity**,
* managing existing **virtual cards**,
* performing **routine actions** while on the move.

It is optimized for **fast interactions** and **read-only or low-friction actions**.

***

#### Functional scope

{% hint style="danger" %}
**Important**\
The mobile app intentionally exposes a **limited but essential feature set**.
{% endhint %}

* Core account data is always available.
* Actions requiring advanced configuration remain web-only.
* The app mirrors the current account state in real time.

This approach ensures **simplicity, stability, and security** on mobile devices.

***

#### Relationship with the web platform

The mobile app works as a **companion interface** to the Aurex web dashboard.

* The web platform remains the **primary control layer**.
* The mobile app acts as a **convenient access layer**.
* No functionality is duplicated unnecessarily.

Users can freely switch between platforms without losing context or data.

***

#### Availability reminder

{% hint style="danger" %}
**Important**\
The mobile application is currently in **beta** and not yet publicly released in app stores.
{% endhint %}

Public release timing and platform availability will be announced through official Aurex communication channels.