Gootax: driver, courier

The Gootax driver app sits in your phone, waiting for a login that only your employer can give. Without that username and password, the screen stays locked — no orders, no map, no way in. This is not a public taxi-hailing app like Uber or Yandex. It is a closed tool built for one purpose: connecting drivers and couriers to the Gootax dispatch platform that their fleet operator already pays for.

Open the app and the first thing you see is not a sign-up form but a login field. That is your reality check. The company you drive for hands you those credentials, and without them, the app is useless. Once logged in, the order feed appears. Available jobs pop up as cards with pickup and drop-off locations, estimated distance, and the fare already calculated by the taximeter. The taximeter does not guess — it reads the tariff structure that your dispatcher configured in the Gootax back-end software. If your fleet runs different rates for rush hour, long trips, or courier parcels, the meter applies them automatically.

This is where the workflow gets interesting. The taximeter and the navigation are not separate features — they talk to each other. When you accept an order, the app pulls the route from your chosen navigation provider (Yandex, Google, Waze, or the built-in 2GIS) and displays the estimated travel time. The fare calculation already includes distance and time-based tariffs, so the route you pick directly affects what the passenger pays. Take a longer but faster highway? The meter adjusts. Get stuck in traffic? The time component ticks up. The app does not force a single route, but it does show you the recommended path based on real-time traffic data from the integrated maps.

Getting started — what actually happens when you log in

After entering your credentials, the app checks your shift status. If you are not on an active shift, the order list stays empty. That catches new drivers off guard — they expect to see jobs immediately, but the app only shows orders when dispatcher has marked them as available. Once the shift starts, the order cards begin flowing. Each card shows the client's pickup address, destination, and the pre-calculated fare. A green button says "Accept." Tap it, and the order locks to your profile. The app then triggers the navigation integration, and the map screen takes over.

The background operation mode is a critical piece. When you minimize the app to check messages or switch to another tool, it keeps running. GPS and GLONASS continue tracking your location, and the taximeter keeps calculating the fare if you are on an active trip. That means you can have the app running in the background while using a separate navigation app, and the fare still updates. But there is a catch — the app requires a constant internet connection. Lose signal in a tunnel or a remote area, and the order feed stops refreshing. New jobs do not appear until the connection returns.

Where the taximeter and navigation clash

The original analysis emerges when you combine the taximeter's tariff logic with the navigation's route suggestions. The taximeter calculates fares based on two inputs: distance and time, each with its own rate. The navigation suggests the fastest route, which is not always the shortest. If you follow the navigation's fastest path, the distance might be longer but the time shorter. The meter then charges more for distance but less for time. The total fare could end up higher or lower than the passenger expected. The app does not warn the driver about this trade-off — it simply displays the final fare after the trip ends. Drivers who do not know their city's traffic patterns can accidentally overcharge or undercharge passengers simply by following the recommended route.

This interaction becomes even messier when GPS signal degrades. The app warns that it may not work correctly on some devices due to poor GPS or GLONASS sensors, firmware issues, or system overcrowding. When the location jumps or freezes, the taximeter can miscalculate distance. The navigation reroutes constantly. Drivers report that the order acceptance screen sometimes freezes entirely during weak GPS conditions, and new orders stop appearing until they restart the app. That is not a rare edge case — it is a documented limitation that the developer acknowledges in the Play Store description.

What the latest update actually changed

The version changelog for the most recent update says one thing: "Fixed the list of available navigators." That is it. No mention of bug fixes for the GPS issues. No note about the order screen freezing. Just a navigator list correction. The developer has not published detailed patch notes for several versions, so drivers are left guessing what else might have changed. Some users on RuStore noted that after a previous update, the order screen would freeze if the phone screen was not locked, and new orders would stop appearing. That specific complaint has not been addressed in the changelog, and it remains unclear whether the current version fixed it.

The app supports multiple map types — several cards, day and night modes, and multilingual interfaces. That flexibility helps drivers in different regions, but the navigation integration itself is not always smooth. The app offers integration with Yandex, Google, Waze, and an internal 2GIS navigator. However, the "fixed list of available navigators" suggests that some navigation options were either missing or incorrectly displayed in previous versions. Drivers who rely on a specific map app may have found it unavailable until this update.

The real-world performance and the SOS button

The app includes an SOS button and a chat with the dispatcher. These are safety features, but they also highlight a tension: the app expects drivers to handle emergencies through the same interface that sometimes freezes. If the order screen locks up, can the SOS button still work? The documentation does not say. The chat function relies on an internet connection, which is already a requirement for the app to function at all. In practice, drivers have reported that the chat can be slow to load, and the cancel button for orders was hidden in a previous update, making it harder to drop a job if something goes wrong.

The bonus program is another point of friction. One user described it as poorly designed and confusing, claiming that enabling it could cost drivers up to 80% of their income. That is a severe claim, and while it comes from a single source, it points to a broader issue: the app's financial features — balance top-up, bonuses, surcharges — are not always transparent. The app allows drivers to top up their balance by bank card, but the flow for withdrawing earnings is less clear. The Gootax website mentions a Cash-it withdrawal service, but that is not integrated directly into the driver app.

The permissions and the technical ceiling

The app requests access to location, SMS/MMS, app data, error reports, diagnostics, and photos/videos. Location is obvious — the app needs it for navigation and taximeter calculation. SMS and photos are less obvious. The app may use SMS for verification or two-factor authentication, and photos could be for uploading vehicle inspection images or receipts. The diagnostics and error reports are standard for crash tracking. But the sheer number of permissions — eight categories — raises questions about data collection. The Play Store notes that the app shares location, personal information, and two other data types with third parties. The data is encrypted in transit, and users can request deletion, but the scope of collection is broad.