Using an Android phone as a sender requires a clear understanding of capability. SEND_SMS is a dangerous permission that needs runtime consent. Notifications make foreground and background status visible, while FCM can deliver server pings or pending-work signals. Bartago uses the platform SmsManager and does not declare Accessibility service because Play Protect can block internet-sideloaded Accessibility apps. Outside the Play Store, APK source, signing certificate, version, and update verification become even more important.
Request permissions just in time
Explain before the system prompt
Show a feature-specific rationale when the capability is first needed. A denial should not crash the app; provide a settings shortcut and a clear limited-mode explanation. Keep permission status readable in the dashboard.
Keep background work visible
Respect operating-system restrictions
Long-running sending should follow Android-supported persistent or foreground work patterns. Provide a visible notification, pause action, and battery-optimization guidance. Do not put secrets or a full contact database in an FCM payload.
- Runtime SEND_SMS consent
- Notification status
- Foreground visibility
- Scoped FCM data
- Immediate disconnect
Authenticate pairing and updates
One-time code; signed APK
Keep pairing tokens short-lived and single-use. Close the web modal after a device connects and allow either end to disconnect. Offer an in-app update only from a trusted HTTPS manifest after checksum and production signing-certificate verification.
Practical checklist
- Permission rationale
- Denied flow
- Foreground status
- Single-use pairing
- Protected FCM token
- Signed update verification
Key takeaway
Trust in powerful Android permissions comes from minimal access, visible operation, and a verified update path.
Final thoughts
On a fresh device, test install, pairing, deny and allow paths, background sending, restart, disconnect, and update. Bartago does not request Accessibility access; the user must review any Android high-volume confirmation. The sender remains responsible for SIM, carrier, and applicable requirements.
Verify consent, provider or carrier policy, and current applicable requirements before launching a campaign.
Start with 100 free automation credits →Common questions
Is accessibility permission mandatory?
No. Bartago neither declares nor requests it and sends SMS through the platform SmsManager.
Does FCM send the SMS?
FCM can signal the device that work is pending; the phone’s telephony capability sends the actual SMS.
Sources and editorial note
- Android Developers: SEND_SMS permission
- Android Developers: persistent background work
- Firebase: receive messages on Android
Last editorial review: August 1, 2026. Legal and policy sections are general information, not legal advice. Verify current requirements with official sources and a qualified adviser.