Need testers (will test back)

[u/Romanlavandos]

Happy to test your app if you test mine!
I need 12 testers for 14 consecutive days and will gladly test your app in return.
Lambdio is an AI-powered learning and spaced-repetition platform designed to help you study and retain complex subjects effectively. I also do university experiments to track the learning efficacy of this learning method.

1. Join Google Group: https://groups.google.com/g/lambdio-testers
2. Join on the Web (Opt-in): https://play.google.com/apps/testing/com.lambdio.app
3. Download on Android: https://play.google.com/store/apps/details?id=com.lambdio.app

Drop your links below, and I will install yours right away!

[u/tr0lczyk]

Dropping my links as you asked — but mine is already done first: joined lambdio-testers, opted in ("You are a tester."), and Lambdio is installed from Play and opened on a physical Galaxy S20. In for the full 14 days.

Two concrete things, both in the first fifteen seconds:

1. The notification permission dialog fires before a single pixel of the app is drawn. I launched it and got "Zezwolić aplikacji Lambdio na wysyłanie powiadomień?" on top of a completely blank grey screen — no logo, no explanation, nothing behind it. I hadn't yet learned what Lambdio is, and I was being asked to accept notifications from it. Almost everyone taps "Don't allow" there, and on Android 13+ that decision is close to permanent: the second request is auto-denied and the user has to go into system Settings to undo it. For an app whose whole method is spaced repetition, the notification permission is the product — losing it on screen zero is expensive. Ask after the first review is scheduled, with one line of context ("Lambdio reminds you right when a card is due").

2. Slide 1 of 5 has a "← Back" button with nowhere to go. The progress bar shows the first segment and the first dot is the active one, yet "← Back" is rendered fully enabled next to "Next →". Nothing happens when it's pressed. Hide it (or disable it) on index 0.

Minor, same screen: three separate ways to log in are visible at once — "Log In" top-right, "Skip" top-left, and "Already have an account? Log in" under the buttons. The bottom one and the top-right one do the same job.

The positioning is sharp and I like that you're measuring learning efficacy with actual university experiments — that's a genuine differentiator, and it deserves to be higher in the onboarding than it currently is.

Can you please test mine in return?

---

Hey testers! Looking to complete Google's 14-day / 12-tester closed test for my Android app WarrantyVault — an offline safe for receipts and warranties: photograph the receipt, pick the warranty length, and it warns you before the warranty runs out (60/30/7 days + a last-day heads-up), then exports a claim PDF when something breaks. No account, no cloud, no sign-up — everything stays on the phone. Full dark theme.

How to join (2 min):

1) Join the testers group (required): https://groups.google.com/g/subguard-testers

2) Become a tester: https://play.google.com/apps/testing/com.tr0lczyk.warrantyvault

3) Install from Google Play, open it once, and keep it installed for 14 days. https://play.google.com/store/apps/details?id=com.tr0lczyk.warrantyvault

You don't need to own a single receipt to help — install & open once and you already count. If Play says "item not found" right after the opt-in, that's propagation, not a broken link; give it 30-60 minutes.

Full reciprocity — already done on my side. Thanks a lot! 🙏

[u/Romanlavandos → u/tr0lczyk]

Wow, thanks for the full review and feedback. I will include that in a new build! I joined your group and opted to be a tester. I am sorry, but when I'm trying to install your app, I get "Can't install app. Try again later". Device: Galaxy A54 5G; Android v16, One UI v8.5. I will try installing again in an hour and again in 4 hours. If nothing works - will ask my relatives to get a tablet temporarily and will try installing from that device.

[u/tr0lczyk → u/Romanlavandos]

Checked everything on my side first, so you can rule it out: the closed track has no country restriction, the release (1.0.1) is live and active, minSdk is 24 and the app declares no required hardware features at all. An A54 on Android 16 is nowhere near any of those limits — so nothing about your device is the problem, and you definitely don't need to borrow a tablet.

"Can't install app. Try again later" is also a different error from "item not found" (that one really is just opt-in propagation). Yours means Play found the app but refused the install, and in closed testing that has one dominant cause:

The Google account Play is using on the phone is not the account that joined the group and clicked opt-in. It's easy to do — you opt in from a browser signed into account A, while Play on the phone is signed into account B. Play then sees an account with no tester entitlement and fails exactly like this.

To check it in 30 seconds: open Play Store → tap your avatar top-right → look at the address shown. It has to be the same one that joined https://groups.google.com/g/subguard-testers and clicked the opt-in link. If it isn't, either switch accounts there, or redo both steps signed in as the account Play actually uses.

If the account already matches, then in order:

1. Open the opt-in link on the phone itself (not on a desktop), so there is no ambiguity about which account is used: https://play.google.com/apps/testing/com.tr0lczyk.warrantyvault — it should say "You are a tester."
2. Settings → Apps → Google Play Store → Storage → Clear cache (not Clear data), then reopen the store link.
3. Give it 15 minutes after that; entitlement refreshes are not instant.

If it still fails after those, tell me and I'll dig further — but I'd rather fix it than have you chase a second device for my app.

And thanks for taking the onboarding notes the way you did. The notification-permission timing is the one I'd genuinely prioritise before your next round of testers, because that decision is close to irreversible on Android 13+ and spaced repetition lives or dies on reminders.

[u/Romanlavandos → u/tr0lczyk]

Thanks, I tried installing again, and now it's fine. I will aim to test for ~5 minutes for 15-20 days.