FatakSeRide is a production-quality Android application for professional ride-hailing and logistics drivers. Its tagline is "Ride Faster. Work Smarter."
FatakSeRide is a driver-focused ride-request filtering and assistance application. The driver selects a supported ride platform, configures filters, uses the target ride app, and FatakSeRide detects relevant ride requests, evaluates them locally, and assists with the appropriate platform-specific action. It is not a generic taxi app and not a mockup: it is a real Android application whose core value is a correct, safe, low-latency decision about whether a detected ride request matches the driver's configured filters, followed by a verified platform-specific action.
The audience is the working driver — a gig-economy professional operating Uber, Ola, Rapido, or Porter on a phone mounted in a dashboard cradle, in daylight and at night, over long shifts. The application is an instrument panel for that driver: fare, distance, decision, and status must be readable at a glance with a thumb, in under a second.
Product priorities, in order, are: 1. Correctness, 2. Safety, 3. Reliability, 4. Low latency, 5. Maintainability, 6. Professional UI/UX.
FatakSeRide runs as a Flutter UI over a native Android Kotlin core. The Flutter layer presents the driver-facing instrument surfaces; the Kotlin layer performs the performance-critical detection, parsing, filtering, decision, action, and verification work. The two communicate over Flutter Platform Channels or Pigeon.
The runtime pipeline is fixed:
Flutter UI
↓
Platform Channel
↓
Native Kotlin
↓
AccessibilityService
↓
Event Processor
↓
Platform Adapter
↓
Ride Parser
↓
Filter Engine
↓
Decision Engine
↓
Action Engine
↓
Verification
Processing is event-driven. The AccessibilityService consumes AccessibilityEvents, the Event Processor debounces and deduplicates them, the active Android package is identified and routed to the correct platform adapter (UberAdapter, OlaAdapter, RapidoAdapter, PorterAdapter — never one universal implementation), the adapter parses a RideRequest from the accessibility tree, the FilterEngine evaluates the enabled filters locally, the DecisionEngine produces a decision, the ActionEngine executes a dynamically located gesture, and Verification confirms the outcome.
Critical processing stays in Kotlin. Ride information is never sent to a server before a filter decision is made. Latency is measured, not claimed.
The sole in-product human actor is the Ride Driver (FatakSeRide operator). A second accepted role, the Developer / QA tester, works in the restricted Test Mode and Developer Mode destinations. All other actors in the system — the target ride platforms, the Android accessibility framework, and the local Room store — are non-persona system or provider actors.
Delivery shape. FatakSeRide is a first-party Android application with custom Flutter UI and native background automation. The application owns its own identity: the driver enrolls once, and their durable state — filters, history, analytics, settings, subscription, account, and assistance state — is bound to that identity and resumes across sessions. The application also owns a background automation surface: the Kotlin AccessibilityService, which runs while the driver uses a target ride app.
Access ownership. The public entry surface (Landing) is anonymously reachable and explains FatakSeRide, its driver audience, and ride-request assistance before identity is established. Identity establishment is self-service: a new driver creates their own account on Sign Up, and a returning driver verifies on Login. Both are anonymously reachable entry states; protected destinations remain unavailable until identity is established. Restricted Test Mode and Developer Mode destinations require authorization for the Developer / QA tester role. The driver-facing operational destinations (Home, Live Rides, Filters, History, Analytics, Settings, Permissions, Subscription, Account, Permission Center, Wallet) require an established driver identity because they read and write durable driver-specific state.
Android permission boundary. FatakSeRide cannot detect or act on ride requests until the driver grants the Android permissions it actually requires and enables the AccessibilityService. The Permission Center and Permissions destinations exist to make that boundary explicit and to show only permissions actually required.
Local-first boundary. Filter decisions are made on-device. Ride information is not sent to a server before a filter decision. History and settings persist locally through Room.
Current vs. future. Everything specified in this document is current. No future-horizon capabilities are defined by the source; nothing in this document should be read as authorizing adjacent capabilities such as account administration, social features, or third-party integrations beyond the four named platform adapters.
Explicit exclusions. FatakSeRide does not continuously screenshot, OCR, or poll the screen every few milliseconds. It does not use one universal adapter for every platform. It does not trigger on home screens, profiles, settings, maps, navigation, completed trips, login, OTP, messages, or unrelated popups. It does not assume the target app is Flutter. It does not blindly assume Accept and Match are the same action. It does not rely on permanent coordinates such as x=500,y=1800. It does not fabricate missing ride data. It does not guess missing required filter values. It does not blindly repeat an action after failed verification. It does not collect passwords, OTPs, unrelated messages, or unnecessary personal information. It does not leave core functionality as fake APIs, simulated acceptance, fake latency, hardcoded success, or placeholder methods. It does not hardcode screen coordinates as the primary interaction method. It does not claim guaranteed one-second performance.
FR-01 — Product identity and tagline (explicit) As a Ride Driver, I should see the application presented as FATAKSERIDE with the tagline "Ride Faster. Work Smarter." so that I recognize the product I am operating.
FR-02 — Driver selects a supported ride platform (explicit) As a Ride Driver, I should select a supported ride platform so that FatakSeRide routes detection to the correct platform adapter.
FR-03 — Driver configures filters (explicit) As a Ride Driver, I should configure filters so that FatakSeRide evaluates detected requests against my criteria.
FR-04 — Assist ON/OFF (explicit) As a Ride Driver, I should turn Assist ON or OFF so that I control whether FatakSeRide evaluates and acts on detected requests.
FR-05 — STOP ASSIST (explicit) As a Ride Driver, I should be able to stop assistance immediately so that no further action is taken on my behalf.
FR-06 — Home session readout (explicit) As a Ride Driver, I should see my session at a glance so that I know how assistance is performing.
FR-07 — Event-driven processing (explicit) As a Ride Driver, I should have FatakSeRide process only relevant accessibility events so that it does not waste battery or degrade the phone.
FR-08 — Package detection and routing (explicit) As a Ride Driver, I should have FatakSeRide identify the active Android package and route it to the correct adapter so that platform-specific behavior is used.
FR-09 — Genuine request detection only (explicit) As a Ride Driver, I should have FatakSeRide detect only genuine active ride/order requests so that it never acts on the wrong screen.
**FR-

Ride Faster. Work Smarter.
Assist On
Avg processing
Filter decisions are evaluated on-device. Average processing time is measured locally, not a guaranteed response time.
Four platforms ship with FatakSeRide. The driver selects a supported platform inside the application — Uber, Ola, Rapido or Porter — and FatakSeRide routes the active package to that platform’s own adapter.
Filter decisions are made on-device. Ride information is not sent to a server before a filter decision.
A new driver creates an account to set up Uber, Ola, Rapido or Porter and define the first filter. A returning driver signs in to reach Home, Live Rides, Filters, History and Analytics.

Ride Faster. Work Smarter.
Assist On
Avg processing
Filter decisions are evaluated on-device. Average processing time is measured locally, not a guaranteed response time.
Four platforms ship with FatakSeRide. The driver selects a supported platform inside the application — Uber, Ola, Rapido or Porter — and FatakSeRide routes the active package to that platform’s own adapter.
Filter decisions are made on-device. Ride information is not sent to a server before a filter decision.
A new driver creates an account to set up Uber, Ola, Rapido or Porter and define the first filter. A returning driver signs in to reach Home, Live Rides, Filters, History and Analytics.
No comments yet. Be the first!