Phone application

Rafik Field for Android

The coach field app supports institution URL sign-in, upcoming events, attendance, assessment results, event completion and recovery. Beta.2 includes updated launcher artwork. It is not the complete web dashboard: program authoring and coach-recorded individual workouts remain web workflows.

Install or build Rafik Field

1. Download the beta.2 Android bundle from the GitHub prerelease.
2. Extract the ZIP in your phone's file manager. Open 1.0.0-beta.2/Rafik-Squire-1.0.0-beta.2-android.apk.
3. Allow installation from that file manager when Android asks. For an existing official installation, update in place; do not uninstall or clear application storage.
4. Open Rafik Field and enter your institution's HTTPS API URL (ending in /api for Compose) and coach credentials. No Metro, Android Studio, computer or USB is required.

The bundle includes SHA256SUMS and build.json with the compiled revision, versionCode and signing fingerprint. Keep the existing signing key for updates. Contributor/fork builds follow the maintained Android release guide; independently signed builds cannot update the official app.

Field timing and completion

Download the schedule and roster online before going offline. Attendance, results and completion unlock at the scheduled start shown in the device timezone. Ask staff to correct an incorrect time through web Schedule. A queued action is saved on the device, not yet confirmed by the institution. Completed events show their acknowledged summary.

Offline work and recovery

Keep the app and its storage intact while work is pending. Exact retries preserve operation IDs; permission changes or conflicts pause replay. Review saved work before discarding anything. An explicitly shared recovery copy contains involved names and training information as plain text, without credentials; share it only through an approved channel. History/corrections require online access.

English and Arabic are supported. Beta.1's founder S20+ standalone/offline acceptance is complete; broader tablet/device/accessibility coverage and historical beta.1-to-beta.2 upgrade preservation remain separate. Packaging checks are not device acceptance. Use synthetic records until the institution approves live data.

Tablets, iOS and API development

Android 7/API 24 is the configured minimum, with ARM64 phones and x86_64 emulators. Tablet usability beyond the recorded coverage is not established. There is no iOS build or store listing.

Build another client against the supported API contract. The institution serves OpenAPI at /v1/openapi.json and bundled Swagger UI at /v1/docs (Compose /api/v1/docs). The viewer documents the supported coach subset; it does not imply every web command is a supported mobile endpoint.

Phone evaluation and signing ownership

Never regenerate an existing update key. Store encrypted backups outside the repository and keep signing secrets out of releases and support messages. See the release guide.