I’m building a no-root Android automation app, and the hardest part may be trust
I’m building ScriptTap, a no-root Android automation app for user-controlled phone workflows.
The app lets people build scripts with taps, swipes, routines, screen-aware checks, OCR/text detection, image/pixel checks, variables, logic, and AI-assisted script creation.
The technical side is hard, but the trust side may be harder.
ScriptTap needs Android Accessibility permission because user-authored input automation requires it. That is a powerful permission, and I do not want to minimize it or hide behind vague onboarding copy.
I’m trying to explain it clearly:
- ScriptTap is no-root.
- Scripts are created and controlled by the user.
- Screen capture is user-controlled.
- It does not bypass Android permissions, lock screens, app security, or consent flows.
- Accessibility is required for overlay/input automation, so users should understand what they are enabling.
My question for other founders:
How would you explain a powerful permission honestly without scaring away every normal user?
I am not looking for fluffy marketing language. I am trying to find the clearest version of the truth that still helps people understand the product.
One thing I've noticed with products like this is that trust often gets framed as an explanation problem.
As though the right wording will eventually make people comfortable.
I'm not sure that's always where trust comes from.
Sometimes people trust a product because they understand it.
Sometimes they trust it because they believe they remain in control even if they don't.
Those can lead to very different decisions about what gets built around the permission itself.
That's what stood out to me reading this.