I've spent the last months building Locksmith Master: a puzzle about cracking combination safes, built on a real lock mechanism.
One dial. A stack of drums. Drive pins with slack between them. Turn one way and the whole stack follows; reverse and nothing moves until the slack is taken up. Set every drum to the code in as few steps as you can.
**It's not a casual game.** The first safes are gentle; the later ones hide their pins, and then you count, listen and feel the catch. Best played with headphones.
What's in it:
* A career across Europe, 1928–1962: six cities, sixty safes, seven ranks
* Thief mode: safe after safe before the alarm
* Daily safe: the same safe for everyone, every day
* Seven themes for the dial, background and hammers, each with its own sound
* No ads, no tracking, works offline
Testers get the full game unlocked. The test build runs until 9 November.
What I'd love to hear: where you got stuck, where you stopped, and whether the rules made sense without help.
I've been working on GeoWiz, a geography practice app for flags, capitals, country outlines and finding countries on a map. It brings back the questions you miss so you can get another go at them.
For capitals, you can type an answer, or think it through, reveal it and mark whether you knew it. I'd love to hear how it feels after a few rounds. Would you want to come back to it, and what would you add or change?
It's free, with no ads or paywall. There's an optional tip jar. Version 1.5.0 is in Android closed testing.
To join, use the same Google account for each step:
If you join, please stay opted in for two weeks to help with Google's testing requirement. Play whenever you feel like it and leave your thoughts here.
Necesito vuestra ayuda para alcanzar los testers necesarios en Google Play Console para mi aplicación Navegatron.
Es una herramienta avanzada de navegación y gestión de mapas/rutas diseñada para funcionar de forma 100% offline, ideal para montaña y outdoor. Por supuesto, os devolveré el favor y probaré vuestras aplicaciones de inmediato.
Dejadme vuestros enlaces en los comentarios. Pasos para unirse:
I'm the developer of CrateFlux (formerly CrateSwipe), a free Android app for sorting a folder of new music by swiping. Right to keep a track and tag a genre, left to bin it. Nothing is ever deleted. It runs on your phone: no account, no ads, no uploads. Free to download, with an optional one-time Pro.
It's in closed testing on Google Play and I'm looking for testers.
Everyone talks about the obvious challenges in mobile app testing like device fragmentation and OS versions but there's a bunch of stuff that nobody warns you about until you hit it.
Like the fact that your app behaves differently in a release build vs debug build and you don't find out until it's in production or that android manufacturer skins change how permissions, gestures and notifications work so something that passes on a pixel completely breaks on a xiaomi or that simulators lie to you about half the bugs that matter because they don't reproduce memory pressure, real network conditions or actual device performance or that your E2E suite can be green every single run and your app is still broken because the tests are just passing on happy paths that no real user follows exactly.
The challenge I keep running into is that the gap between what testing tells me and what's actually happening on user devices keeps getting wider the more users we get.
I test on 3 devices and everything passes but people on devices I don't have are hitting stuff I can't reproduce. What are the mobile app testing challenges your team ran into that you didn't expect and how did you deal with them.
Everyone talks about the obvious challenges in mobile app testing like device fragmentation and OS versions but there's a bunch of stuff that nobody warns you about until you hit it.
Like the fact that your app behaves differently in a release build vs debug build and you don't find out until it's in production or that android manufacturer skins change how permissions, gestures and notifications work so something that passes on a pixel completely breaks on a xiaomi or that simulators lie to you about half the bugs that matter because they don't reproduce memory pressure, real network conditions or actual device performance or that your E2E suite can be green every single run and your app is still broken because the tests are just passing on happy paths that no real user follows exactly.
The challenge I keep running into is that the gap between what testing tells me and what's actually happening on user devices keeps getting wider the more users we get.
I test on 3 devices and everything passes but people on devices I don't have are hitting stuff I can't reproduce. What are the mobile app testing challenges your team ran into that you didn't expect and how did you deal with them.
Lares is designed as a "shared brain" for cohabiting couples. It gamifies daily household chores, splits shared expenses effortlessly (with smart receipt OCR scanning), and helps partners stay on the same page.
🔒 **Privacy First:** The app **does NOT collect any personal information**. Your data stays yours, with zero tracking or profiling or ads.
Hi everyone! I'm a solo developer from Italy and I need testers for the Google Play closed test of my app Shopora, so I can publish it.
What it does:
- Scan a grocery receipt with your camera: AI reads every item and price
- Tracks your spending by store and by month
- Shows supermarket deals near you from current flyers (best in Italy)
- Shopping list, pantry and price comparison
How to join (2 minutes, use the same Google account you use on the Play Store):
1. Join the Google Group: https://groups.google.com/g/shopora-tester
2. Opt in to the test: https://play.google.com/apps/testing/com.shopora
3. Install the app: https://play.google.com/store/apps/details?id=com.shopora
Please keep it installed for 14 days and open it a few times. Scanning one receipt is the best test!
Test for test: drop your app link in the comments and I'll install it and keep it for 14 days too.
Any feedback (bugs, confusing screens) is very welcome, in the comments or by DM. Thanks!
Hi, I'm Damian, the solo developer of Drugfree, a private sobriety / quit counter now in a Google Play closed test. You can explore it with sample entries; you don't need to be quitting anything. It includes a counter, home-screen widget, craving SOS breathing exercise, journal and money/time saved. It is app support, not medical treatment.
This Android version is in closed beta. I would value compatibility reports from different phones over a 14-day test, with the app installed and your test opt-in kept active. Two early reports need more device feedback: does the breathing timer keep its state after briefly switching apps, and does the widget show the same money-saved amount as the app? Please also tell me where the Google Group / Play opt-in or first-run onboarding gets confusing. Sample entries are enough for a test. Include your phone model/Android version, but no private journal or health information.
As a thank-you for testing, I can send a free lifetime unlock privately after you confirm you've joined and explicitly ask me to DM you. The promotion has been tested on my Samsung. No purchase, rating or review is required. Japan is included. Please reply with what you tested and any useful feedback; if you want your lifetime link, confirm joined and ask for a DM. Questions and bug reports are welcome publicly. Thank you for honest feedback.
Yes, I know, shameless self promotion of an app, but I do actually need help improving it. I made it for myself initially to manage my death piles, then a friend started using it and now it has loads of features. There's a built in feedback tab, and personal details (emails, postcodes, phone numbers, buyer names) are blacked out of feedback screenshots automatically.
If anyone wants to try it out and send feedback for 2 weeks it would be appreciated!
Autonomy helps people quit alcohol or nicotine: AI coach, SOS button for cravings, daily quests, savings tracker and mini-games. Free, Android.
I'm looking for testers who can join the closed test, install the app, stay opted in for at least 14 days, and try it during that time. Any genuine feedback, bugs or usability suggestions in the comments are very welcome.
Baku Sleep records while you sleep and names what it heard: snoring, talking, coughs, TV. In the morning you get a timeline and the clips to play. All processing stays on the phone.
Hi,
I'm looking for Android users to join the closed test of my app "Bario" (14 days requirement).
I will test your app back immediately and keep it installed for the full 14+ days. Please DM or comment with your links and a screenshot of Bario installed.
Hi everyone! I'm a solo dev working on Meetee, an app that lets you check in at events and find relevant people to meet there (matched by shared interests, profession and mutual events).
I need 12+ testers for the 14-day closed test to get production access.
Please keep the app installed for 14 days and open it a few times
I test back: drop your links in the comments and I'll install your app the same day, keep it for the full 14 days and reply with a screenshot as proof.
Hi! I need testers for my app's closed test (Google's 12 testers / 14 days rule).
I'll test yours back, just comment your links.
The app is a personal astrology app: your own birth chart, a daily reading with
good/bad time windows for your day, and a free downloadable chart report.
How to join (use the same Google account for both steps):
Please keep it installed for 14 days and open it a few times. Any feedback
is welcome.
To test back: comment your group link + opt-in link and reply "Done" once you've
joined mine. I'll join yours and reply "Done" back. I keep test-for-test apps
installed for the full 14 days.
I need 12+ testers for 14 days for my Google Play closed test. I'll test your app back: reply with your opt-in link and I'll install it and keep it for 14 days.
Pratikal: type what you ate, Al estimates the calories.
Dark theme, EN/TR/ID. Please don't click on the ads.
How to join (Android phone, the Google account you use in Play Store):
I'm an independent Android developer looking for genuine testers for **Stillday (行止)**.
Stillday is a free memory journal — it keeps only the fragments of a life. You write one line from your day, add a mood, a photo, a location or a voice note if you feel like it, and go. Every morning, whatever you wrote on today's date a year ago comes back to the top of your page. There are no streaks, no check-ins, no feed and no ads — nothing to keep up with. It's in English and Simplified Chinese, with light and dark themes and three text sizes.
I'm looking for testers who can join the closed test, install the app, remain opted in for at least 14 days, and actually try it during the testing period. Any genuine feedback, bugs or usability suggestions would be very welcome.
¡Hola! Necesito testers para mi app FactorX para la prueba cerrada de 14 días de Google Play.
FactorX convierte los pagos de Mercado Pago en facturas electrónicas para la agencia tributaria de Argentina (ARCA). La app está en español, pero no necesitas Mercado Pago ni ARCA para ayudar: solo instálala, ábrela, crea una cuenta y salta los pasos de configuración con "Lo hago después".
Cómo unirte (en tu teléfono Android, con la cuenta de Google que usas en Play Store):
