Google Play testers
This is a guide for internal testers only.
This page explains how to join Closed Testing for Heartbeater by Floert and install the Android app from Google Play.
Heartbeater is in Closed Testing on Google Play (not a public listing yet). You still need to join the test program and use the same Google account you gave us.
How to get set up as a tester
If you want to join Android beta testing, email [email protected] with the subject line Sign-up Request for Heartbeater Android Testing.
Tell us the email address you use on Google Play. If that address is different from the email you send from, include the Play Store email in your message so we can add the right account.
We will add you to Closed Testing and reply when you are set up. Then continue with the steps below.
Before you start
- Sign in to Google Play with the same email you sent us for tester setup. Tester access is tied to that address. A different Play account will not see the test build.
- Use an Android phone or tablet that is logged into that account (Play Store and the browser you use to accept the invite).
- Wait a few minutes after you become a tester if the listing is not there yet.
Verify your Google Play email
Confirm the account you gave us matches the one active in Google Play:
On an Android device
- Open the Google Play Store app.
- Tap your profile icon (top-right).
- Look directly under your name for the active email address.
- Tip: If you have multiple accounts on the phone, tap the arrow next to the email to switch accounts.
On a web browser
- Go to play.google.com/store/apps.
- Click or tap your profile icon (top-right).
- Your active Google email is listed at the top of the menu.
That email must match what you sent us for tester setup.
1. Accept the tester invitation
Heartbeater is in Google Play Closed Testing — that is Google’s name for this stage.
Open this link on your Android device (or on a computer signed into the same Google account):
https://play.google.com/apps/testing/com.heartbeater.app
Tap Become a tester on the invitation page.
When enrollment has worked, you should see that you are a tester for Heartbeater, with a link to download it on Google Play. Use that link to install on your Android device(s). It can take a little while before the listing appears.
This step can fail — the download link sometimes opens a dead listing. If that happens, use the next sections.
2. If Play Store says “Item not found”
The download it on Google Play link from the Closed Testing page sometimes opens the Play Store on a missing listing (“Item not found” / sad satellite). Try again does not fix it.
Do this instead: open the listing by package name, as in the next section. Thanks for sticking with us at this stage.
3. Find the app by package name
In the Play Store app or at play.google.com (still logged in under the account you gave us), open:
https://play.google.com/store/apps/details?id=com.heartbeater.app
Or search for:
com.heartbeater.app
You should see Heartbeater / Floert. Open that listing and install from there.
4. Install and first launch
- From the listing, tap Install.
- On first launch, allow Bluetooth and Nearby Devices (and Location on older Android) so BLE discovery and advertising can run.
- Set your profile (age 18+, interests, signature icons) on the Profile tab, then open Discover to scan.
- For best tests, use two physical Android devices (or one Android + one iPhone with the App Store build) nearby — the emulator is limited for advertising/RSSI.
5. What to try
- Discover radar / heartbeat intensity as you move closer or farther
- Matches and All tabs with real nearby peers
- Safety Mode (long-press / triple-tap) and Block / Report
- Audio and vibration toggles in Settings
- Background behavior with the persistent notification / foreground service
If something still fails
Email [email protected] · or use Support / Contact.
When reporting a bug, please include:
- Android device model
- Android version
- Heartbeater version (from About / Settings if available, or Play Store listing version)
- Whether Bluetooth / Nearby Devices / Location permissions were granted
- What you expected vs what happened (screenshots help)