# Technical Notes

> **Note**\
> This subsection provides technical and platform-level information related to the Aurex mobile application.

The Aurex mobile app is implemented as a **client interface** on top of the existing Aurex infrastructure and does not introduce a separate backend or data model.

***

#### Application architecture

The mobile application operates as:

* a client consuming the same backend services as the web dashboard,
* a stateless interface where critical logic is enforced server-side,
* a synchronized access layer for existing Aurex accounts.

This ensures consistent behavior across platforms.

***

#### Backend integration

{% hint style="info" %}
**Important**\
The mobile app connects to the **same backend environment** as the web platform.
{% endhint %}

* No sandbox or mobile-specific backend exists.
* All actions are validated using the same business logic.
* Data returned to the mobile app is identical to web responses.

***

#### Data synchronization

Account data is synchronized automatically.

This includes:

* wallet balances,
* card balances and status,
* transaction history.

> **Note**\
> Temporary network issues may delay updates but do not affect data integrity.

***

#### Platform support

The mobile app is built as a **cross-platform application**.

* iOS and Android are supported
* Feature availability may depend on OS-level capabilities
* Performance may vary across devices

{% hint style="warning" %}
**Important**\
Official system requirements will be published closer to the public release.
{% endhint %}

***

#### Network dependency

{% hint style="info" %}
**Important**\
The mobile app requires an active internet connection for all critical operations.
{% endhint %}

Offline usage is limited to previously cached, non-sensitive data.

***

#### API usage

* The mobile app does not generate or expose API keys.
* All API communication is handled internally.
* API access for integrations remains web-managed.

***

#### Limitations

* No account registration within the app
* No offline transaction execution
* No developer or integration settings

These limitations are intentional and align with the platform’s security model.

***

#### Summary

* Mobile app = client interface
* Web platform = configuration and onboarding
* Backend = shared and authoritative