User guide · 13/15
Mobile app & web edition
What the two editions share, how they differ, and how to move an academy between them.
Same rules, same data
The Android app and the web edition implement the same model: the same fourteen tables, the same balance formula, the same session-credit rule, the same archive cascades, the same alert keys, the same referral milestones and the same backup format. A backup made on either restores on the other.
| Android app | Web edition | |
|---|---|---|
| Where data lives | On the device, offline | On your server, in a Docker volume |
| Users | One | Administrator account, sign-in, sessions |
| Reach | The device only | Any browser, phone to desktop |
| Backups | Files in the app folder, shareable | Files on the server, downloadable |
| Automatic checks | When the app is open | Every 15 minutes, always |
| Automatic backup | While the app is open, after the set time | Daily on the server |
| Languages | Per build (en/ar or fa/en) | en, ar, fa, configurable |
Moving from the phone to the web
- On the phone: Settings → Backup → Create backup, then share the
.ambakfile to yourself. - On the web: Settings → Backup → Restore backup, upload the file, enter the password.
- Check the dashboard counts and a few balances; they should match the phone.
Keeping both
Some academies keep the phone at the front desk and the web for the office. Take a backup on the edition that changed and restore it on the other; the last restore wins, so decide which edition is the source of truth for each period.
Photos
Learner photos travel inside the backup, under photos/, and are restored to the same relative path on either edition.