Looking for serious Android beta testers for Neurolic — private on-device AI memory
Hey Indie Hackers,
I’m looking for serious early adopters to test the current beta version of Neurolic.
Neurolic is a private Android AI app designed to run on-device and become a personal memory system.
The idea is simple:
You save notes, transcribe recordings, and use chat/search to recall what matters later — without relying on a cloud-based AI workspace.
You can use it to:
- Save notes you want to remember
- Transcribe recordings into searchable memory
- Ask general AI questions in Chat
- Search and recall information from your saved notes and transcriptions
This is not a polished mass-market launch yet.
This is an early beta, and I’m looking for people who understand what that means: testers who are willing to use the app properly, find weaknesses, give blunt feedback, and help shape Neurolic into something genuinely useful.
I’m especially interested in feedback on:
- Was the setup clear?
- Was the app useful enough that you would open it again?
- Was recall/search accurate when you asked about your notes or transcriptions?
- What felt slow, confusing, or unnecessary?
- What would you change or add to help shape Neurolic into something you would actually use?
Important details:
- Android only for now
- Please install on Wi-Fi because the model/dependencies are large
- Notes and transcriptions can take a few minutes to process
- This is an early version, so honest feedback matters more than polite feedback
I’m looking for 20–50 serious early adopters.
People who help test this beta properly and give useful feedback will get free access to future Neurolic features when the app becomes a paid product.
To join the beta, email me at:
Please include:
- The Gmail address linked to your Android / Google Play account
- Your country
- How you plan to test Neurolic — notes, transcription, work, study, meetings, ideas, memory recall, etc.
Important: the Gmail you send must be the same Google account you use on your Android device, or you need to clearly include the correct Google Play email. Otherwise I may not be able to add you to the beta.
Google Play link:
https://play.google.com/store/apps/details?id=com.neurolic
If you’re the kind of person who likes testing early products and helping shape them before they become polished, I’d genuinely value your feedback.
This is a strong beta ask because you are filtering for serious testers, not just downloads.
One thing I’d tighten is the testing path. Right now the product has a lot of possible use cases: notes, recordings, study, meetings, ideas, memory recall. That is useful, but early testers may give scattered feedback unless you guide them into a specific test loop.
I’d probably split testers into 3 groups:
people who take notes daily
people who record meetings/classes
people who need personal recall/search later
Then give each group one clear task, like “save 10 notes over 3 days and ask 5 recall questions” or “transcribe 2 recordings and search them later.”
That will give you sharper feedback than general beta usage.
Also, since this may become paid later, I’d watch for one signal above everything: not whether people say it is useful, but whether they naturally come back to search their own saved memory again.
Hello Aryan,
this is the plan, the email that i will send to each individual will be specific but the problem i am struggling to get people on board. People don't seem to be interested in being early adopters. Do you have experience in this domain?
Yes, a bit.
The thing I’d be careful with is assuming the problem is simply “people are not interested in being early adopters.”
Usually the harder problem is that the first tester path is mismatched to the moment when someone actually feels the pain strongly enough to tolerate beta friction.
For something memory/notes-related, the wrong early users can make a useful product feel unwanted very quickly.
I would not try to solve that casually in the thread because the first-tester path changes who you target, where you find them, and what you ask them to do first.
If useful, share your email and I’ll send the tighter first-tester path in a way you can actually use. This is the kind of thing that tends to work better as a clean written pass than scattered thread advice.
For Android beta testers, “serious” usually means giving them one concrete trust/performance task, not just asking them to browse around. For Kinetic Override I’d ask testers to grant the permission, record one short tap/swipe loop, replay it twice, then note where timing, wording, or local-data trust felt unclear.