Google Play release — interest check & closed-beta testers wanted 🧪

## Amply on Google Play?

I'm considering bringing Amply to Google Play. Before a new app can go to production
there, Google requires developer accounts like mine to run a closed test with at
least 12 testers opted in for 14 consecutive days. This issue is for gauging interest
and finding those testers.

### 1. Show interest 👍

React with 👍 on this issue if you would install Amply from Google Play.
Reactions only please, no "+1" comments.

### 2. Join the closed beta

Want to actively help?

1. Email **support@darken.eu** with the subject "Amply beta" and include the
Google account email you use with the Play Store. That may not be your normal
contact address, and it's the one I need to add you to the testing track.
2. Once the beta track is live, you'll receive an opt-in link. Install Amply through it.
3. Keep the app installed and stay opted in for the full 14 days, and send at least
a short line of feedback. "Device X, works" is enough, device reports also help
expand supported-device coverage.

Everyone who completes these steps gets a free upgrade code for Amply Pro once
Pro launches.

Your email address is only used for beta enrollment and delivering the upgrade code,
and is deleted afterwards.

### Notes

- Timing depends on Google's app review. Amply declares a special foreground-service
use case (required to reliably restore your charging policy) that Google has to approve.
- There will likely be an Amply Pro upgrade with extra features, e.g. the home-screen
widget and charge history. The core app stays free: temporary full-charge sessions
with automatic policy restore, the reconnect gesture, and the notification controls.
- The Play release changes nothing about the open-source version. Amply stays GPL-3.0,
the GitHub release channel remains, and the GitHub version will get an optional
sponsor flow like my other apps.

This issue is an interest check and request for Google Play closed-beta testers, not a code change. No files, tests, or entry points are identified; completion means opting into the beta for 14 days and sending feedback if the testing track becomes available.

Written by the indexing model from the issue text.