<aside> 💡

This is a living document that will be updated as the MyArkansas testing strategy evolves and expands.

Detailed notes for the latest Android/iOS alpha: MyArkansas 2026.04.1-alpha.

</aside>

Overview

This document covers how to access, test, and provide feedback on MyArkansas app builds. It applies to two testing tracks:

• Alpha
• Beta

Both tracks currently point to the staging environment (UAT in Resident Engagement Platform). This is important to note, as data/content in UAT may not match what is available in production.

Testing Tracks

Alpha

• Who: Trailhead Labs team + Tyler Technologies staff + select State of Arkansas staff.
• Purpose: Catch bugs, validate new features, and stress-test functionality before wider release.
• Build Cadence: As needed — alpha testers may receive frequent builds, sometimes multiple per week.
• Expectations: Alpha builds may be unstable. Crashes, incomplete features, and UI rough edges are expected.

Beta

• Who: A larger group of State of Arkansas employees, and potentially members of the public.
• Purpose: Validate the app experience with real users in near-production conditions.
• Build Cadence: Less frequent than alpha. Beta builds represent features that have already passed internal testing.
• Expectations: Beta builds should be relatively stable, but bugs are still possible (that's the point of testing!).

Getting Access

Android (Alpha)

Prerequisites