Our beta only works if testers come in pairs. How would you recruit for that?

Family Ping is a check-in app for families: one person taps once to say they are home and okay, and one trusted helper sees it. No live map, no location history, and nobody can put it on your phone without you typing a pairing code.

It is in review on both stores. Before it goes public I want it used by real families, because a safety app tested only by the person who built it is not a safety app.

Here is my actual problem: it cannot be tested by one person. A solo tester installs it and there is nothing to see — no second phone means no pairing, no status, no notification. Every signup that is not a pair converts to zero sessions.

So, two things.

1) If you want to try it, bring someone. A partner, parent, sibling, flatmate — anyone who would genuinely want to know you got home.

iPhone (TestFlight, open now): https://testflight.apple.com/joi...

Android: open testing is in review at Google, a few days away.

What to test and what I most need to hear: https://familyping.editerra.se/b...

The single most useful report is anything the app states that is not true — wrong place, stale timestamp, "okay" when it should not be. Second most useful: whether an SOS notification actually arrives on a locked phone. That is the one path I have not been able to confirm end to end.

2) The question I would genuinely like answered: how do you recruit testers for something that needs two people at once? Most beta-recruiting advice assumes a single user. Seed one side first, referral mechanics, pairing strangers up — has anyone here solved this?

And the argument I keep having with myself: is "less data" actually a feature people want, or does everyone secretly want the map?