3TM

Opening the App: The First Screen You See

The moment you tap the 3TM icon, you are greeted with a map view of Tashkent. No splash screen, no welcome message. Just a zoomable map with bus stops marked as small icons. The app assumes you already know what you are looking for. Below the map, a search bar invites you to type a stop name or address. The design is functional, not flashy. The colors are muted, the fonts are readable, and the buttons are large enough for a phone screen. There is no attempt to be "modern" or "sleek" — it is purely utilitarian. This matches the app's stated purpose: to provide real-time bus information, not to entertain. The real-time data access promise is visible immediately. When a bus approaches a stop, its icon moves on the map in near real-time. This is the core utility that keeps users coming back, despite the app's obvious lack of polish.

Once you tap a stop, the app displays a list of routes that pass through it, along with the estimated arrival times for each bus. The times are shown in both text and graphic formats — a small bar chart that fills up as the bus gets closer. This visual cue is helpful for users who prefer a quick glance over reading numbers. The favorites feature allows you to save specific stops and routes, so you do not have to search for them every time. For a daily commuter, this is a time-saver. One less search, one less tap.

Bus Occupancy and Arrival Times: A Feature That Works Together

Here is where the app reveals a useful integration. The bus occupancy indicator and the intelligent arrival calculation system are separate features, but they complement each other in a practical way. When you check the arrival time for a bus, you can also see how full it is — represented by a small icon showing a bus with varying levels of passengers. This is not just a gimmick. A user waiting at a crowded stop can see that the next bus is already 80% full and decide to wait for the next one, which might be less crowded. The app does not automatically suggest this, but the information is there for you to use. This is a subtle efficiency that most users might not notice, but it reduces the frustration of boarding a packed bus.

On the other hand, the route building system and the favorites feature do not talk to each other as seamlessly. You can build a route from point A to point B, and the app will show you the bus numbers and transfer points. But if you have saved a favorite stop, the route builder does not automatically use it as a starting point. You have to manually select the stop from the map or search for it again. This is a missed opportunity for integration. The data is all there, the features are both active, but the app does not connect the dots. A user who frequently travels from home to work would benefit from a one-tap route based on their saved favorites. The app does not offer that. The original analysis here is that while the app is built as a collection of independent tools, the underlying architecture allows for cross-feature data sharing — but the user interface does not always expose these connections. The result is an app that works perfectly for single tasks but feels disjointed when you try to use it for complex workflows.

Real-World Performance: Accurate Tracking, but Limited Feedback

The app's performance is generally reliable. On a 4G connection in Tashkent, the bus positions update every few seconds. The arrival times are calculated using an intelligent system that considers traffic jams, delays, and the time of day. This is a standout feature for a non-commercial project. According to the changelog, the route building system was recently reintroduced after a period of absence, which suggests the developer is actively maintaining the app. However, the app does not offer much in terms of user feedback. There are only 107 reviews on the Play Store, and many of them are in Russian or Uzbek. The developer does not respond to reviews, and there is no official support channel. This lack of transparency is a recurring frustration for users who want to report issues or suggest improvements. The app is stable, but it feels like a black box — you do not know what changed, and you cannot easily find out.

One notable limitation is the offline access. The app requires an internet connection to load bus positions and arrival times. There is no offline mode, no cached data for previously viewed stops. If you lose connectivity, the app becomes useless. This is a deliberate trade-off: real-time tracking requires a constant connection. For a user in central Tashkent with reliable internet, this is acceptable. For a user in a remote area or on the metro, this could be a dealbreaker. The app simply does not function offline, and that is a technical limitation that is baked into its architecture from the ground up.

Permissions and the "Quick Stop" Feature

The app requests a minimal set of permissions. On Android, it asks for network access, foreground service, and wake lock — all necessary for real-time tracking. It also requests write to external storage, presumably to cache map data and stop information. The Exodus Privacy report does not list any trackers, which is a positive sign for a non-commercial project. The app does not collect or share any personal data, according to the Play Store's data safety section. This is a strong privacy posture for a transport app. The "Quick stop" feature, mentioned in the latest changelog, appears to be a shortcut that allows users to quickly check the arrival times for their favorite stops without navigating through the map. This is a small but thoughtful addition that saves time for frequent users. However, the feature is not clearly documented, and it is not obvious how to enable it. A user might overlook it entirely. That is a specific design choice that prioritizes simplicity over discoverability.