Testing Android APKs

Fraser can run personas against an Android build by uploading an application package (APK file).

You may only upload APKs you own, operate, or are expressly authorized to test. Do not upload malicious, unlawful, or third-party APK files. Lythe may scan, restrict, reject, or remove uploaded files to protect the Services, users, or third parties.

When to use it#

APK testing suits the same questions as web flows, onboarding friction, unclear state, accessibility barriers, but for a mobile build where the constraints are tighter: smaller targets, less room for explanation, and users who are typically more distracted.

Preparing a build#

• Upload a build that reaches the flow you care about without requiring credentials the persona can't have. If the flow is behind auth, supply a test account.
• Prefer a build close to what ships. Debug builds with placeholder data produce findings about the placeholder data.

Persona selection on mobile#

Mobile amplifies impatience and accessibility issues. A sensible default:

• Impatient multitasker: mobile users are rarely giving you full attention.
• Screen-reader user: touch targets and labels break more often on mobile.

What to expect in findings#

Findings map to screens and steps within the app, the same shape as web:

Finding:  Missing workspace-created confirmation
Detail:   After creating a workspace, no confirmation state is shown,
          so the user is unsure whether the action succeeded.
Fix:      Show an explicit success state before returning to the list.

Limits#

Simulation against a build is an evaluation aid, not a device-lab substitute. It won't replace real-device performance testing, crash reporting, or store-compliance review.

Testing an iOS build instead? See Testing iOS builds.

See Authorization & limits.