One line of Gradle. No more daily screenshots.

Add this to your app module's build.gradle.kts, then sync Gradle. It supports Android 7.0 (API 24) and up.

dependencies {
    implementation("app.getfourteen:sdk:1.0.1")
}

There's no setup code. The SDK starts itself and does nothing until a tester connects through Fourteen or an invite link, so anyone else who has your build isn't measured.

Use implementation, not debugImplementation, because testers install your release build from Google Play. Upload it before day 1, and tell Fourteen you've added the SDK during app setup.

Install your build on the phone with Fourteen, then tap Check my build during setup or on My test. Fourteen opens your app, and the SDK reports in once. If your build doesn't have the SDK, you'll be told right away. The check doesn't count as testing, and your phone doesn't stay connected.

Once the test starts, testers start your app from Fourteen, which connects the SDK the first time. A day counts once a tester has at least 60 seconds of active use and 5 touches. Their square then fills in on your My test tab, which can take a moment after they leave the app.

To check a device directly, show this on a debug screen:

val status = Fourteen.status()
// status.paired, status.registered, status.todayActiveSeconds,
// status.todayTouches, status.todayCompletedTasks

Call this at the point where the action really succeeds, not when a button appears on screen:

import app.getfourteen.sdk.Fourteen

fun onRouteSaved() {
    Fourteen.completeTask("saved_route")
}

Names can use letters, numbers, dots, dashes, and underscores, up to 64 characters. Calls are ignored for anyone who isn't a connected tester.

1. In Fourteen, open My test, then Tasks.
2. Tap Edit on an upcoming day, since days that have started can't be changed.
3. Enter the same name, such as saved_route, under Task event.

To check them, tap Test my events on the Tasks screen. Fourteen opens your build on your phone, you do each action, and it shows which events it heard, matched to your tasks. This doesn't count as testing, and only the event names are kept.

To list every call in your code, including ones that haven't run yet:

grep -rn "Fourteen.completeTask" app/src

Testers see Task confirmed when the event arrives. On your Results tab, tap an area to see who finished it each day, with a check on anyone your app confirmed.

A tester still gets credit for active use if the event never fires, so a bug in your app can't count against them.

Crash reports

Crashes are grouped by error on your Results tab, with build, Android version, and which testers were affected. If you use another crash tool, such as Crashlytics, it keeps working.

If your release build uses R8, class and method names in these reports are shortened. Use your mapping file to read them, or keep them readable in your test build.

Verified Play installs and device coverage

Fourteen shows how many testers installed through Google Play, plus which phones, Android versions, screen types, and countries you've covered. An install check doesn't prove someone is still opted in, so Play Console remains the source of truth.

In-app bug reports

Connected testers can shake their phone to send you a note from inside your app. To add your own button too, call:

Fourteen.openBugReport()

Questions you'll need to decide

• Location: the SDK sends the phone's country setting, not a location reading, and doesn't use location permissions. Decide whether you treat that as location data.
• Sharing: Google says transfers to a service provider working on your behalf generally don't count as sharing. Consider how that applies to your test, since Fourteen stores this data and group members may see test status.
• Purpose: this data is used to confirm testing, show you results, and find problems in your app.
• After the test: once the SDK is out of your production build, update your form to match.

Data travels over HTTPS. Testers with a Fourteen account can delete it at getfourteen.app/delete-account.

Remove the SDK from your production build

Delete the dependency and any Fourteen calls. Or, if you'd rather keep the calls in your code, swap the dependency for the stand-in, which has the same functions and does nothing:

implementation("app.getfourteen:sdk-noop:1.0.1")

Only collected from connected testers

• A tester ID that doesn't contain a name or email, your package name, and your version number
• The date, active time, number of sessions, and number of touches
• The names of any tasks you report
• Phone maker and model (such as Google Pixel 8), Android version, phone or tablet, the phone's country setting, and whether the app came from Google Play
• Crashes: the error type, code location, and count, but never the error message
• Bug reports: the tester's note, plus a screenshot only if they see it and choose to send it

Apart from a screenshot a tester chooses to send, it doesn't collect screen contents. It also doesn't collect what testers type outside the report form, where they tap, contacts, location, advertising IDs, or account details. It adds the INTERNET and ACCESS_NETWORK_STATE permissions.

You're responsible for your own app's disclosures, including Google Play's Data safety form, while the SDK is in your app. See the privacy policy for details.