Why Accessibility Is Required

Resumo: A direct explanation, for reviewers, of why Valeu’s core functionality is not possible without the Accessibility Service.

Problem

Rideshare drivers receive ride offers that must be accepted or declined within seconds. The offer’s fare, distance, and estimated time are shown only inside the ride-hailing app’s own interface — there is no public API that exposes this information to third-party apps.

Need

To calculate ride indicators (fare per km, fare per minute) and support the driver’s decision, Valeu needs to identify when an offer is displayed and process the relevant text from it, in real time.

Why Accessibility

Android’s Accessibility Service is the platform-provided mechanism for accessing the UI information required to process ride offers. It is the only mechanism that allows Valeu to process offer information without requiring the driver to manually type it in under time pressure.

Why Overlay

Once the offer is processed, Valeu needs to display the result somewhere visible to the driver, without switching away from the ride-hailing app. The “display over other apps” permission is what enables this floating result panel.

What is NOT done

• No gestures, clicks, or input are injected into the ride-hailing app.
• No content from apps other than the supported ride-hailing apps is processed.
• No continuous screen recording or screenshot storage takes place.

Privacy

Processing happens on-device, scoped strictly to ride-offer events. See Data Safety and Privacy Compliance for details.

Related articles

• Accessibility Declaration
• Overlay Permission
• Data Flow