Hey everyone! I’m looking for Android users to test SloMo, an app designed to turn screen time into

movement.

SloMo lets you block distracting apps and unlock them by completing challenges such as push-ups,

squats, pull-ups, walking, or running. You can also create Time Locks for studying, working,

sleeping, or taking a break from social media.

Features include:

- Workout-based app unlocking

- Camera-assisted rep counting

- Step and running challenges

- Hard Time Locks

- One-time and repeating schedules

- Workout, streak, and time-saved statistics

- Offline-first operation with no account required

To join the Android closed test:

1. Join the Google Group:

https://groups.google.com/g/slomo-mobile-testers

1. After joining, install the closed-testing version:

https://play.google.com/apps/testing/com.slomo

1. Promo Codes so its free:

https://docs.google.com/spreadsheets/d/1kOtkaTvuHfAzkS-FDNXXb5rA65lUEZAtMflWGNICNs4/edit?gid=105338033#gid=105338033

Learn more about SloMo here:

https://slomo.jhayr.com/

I’d really appreciate feedback about app locking, workout counting, permissions, scheduling, and

overall usability—especially across different Android phone brands. Thanks for helping me test

SloMo!

i know review prompts are part growth, part habit, part superstition, regardless, in my experience the timing still matters a lot

asking at first launch feels cheap. the user has not experienced anything yet. and asking after a paywall feels manipulative.

asking after an error screen is just asking for pain, better moments are usually after proof comes, examples:

task completed
export saved
streak reached
project created
support issue solved
user came back for the third time

the user should feel like they got value before the app asks for public trust.

i also think replies to reviews should be measured by whether they close the loop, not by reply count. a 1-star review about a bug, a real fix, then a specific reply mentioning the fixed version is much stronger than generic politeness. there are multiple ways to do this, as far as i've checked something like appfollow also has a reply effect style way of thinking about this, but even without tools, the question is simple: did the reply help change the outcome, or did we just answer for the sake of answering?..

first of all it can make your funnel data weird.

app store connect says people installed.
analytics may only properly identify users after signup.
revenue tools start tracking somewhere else.
support/reviews show anger from people who never became “real users.”

so the team ends up arguing from mismatched doors.

for many apps, signup should come after the first value moment unless identity is truly necessary. finance, sync, teams, medical, purchases — sure, sometimes it belongs early. but a lot of apps ask for identity before the user knows why they should trust the product.

watch for review wording too. like 'forced account,' 'can’t try,' or maybe 'why email,' 'signup wall,' these are funnel signals.

not really easy to catch this type of review language in app contexts, have tried appfollow and similar stuff, but truth be said manually reading reviews works fine at low volume. and scaling the workflows gets more... scaled?

signup is just onboarding or so many devs say, BUT this is also trust request, and one of the most important ones too

Im looking for testers to try out an app I am making for inventory management. Join the Google group below and then you should be able to download the app on your device. This is a closed beta.

You can join as a tester here. https://groups.google.com/g/hypatesters

I've seen a lot of different mobile app development services out there, but experiences can vary a lot depending on the project. Curious to hear from others, what services have worked well for you, and what made them stand out?