KROOZ

Directly Inside the Ride Request Workflow

Opening the KROOZ app drops you straight into the ride request screen. No lengthy tutorial. The first thing you see is a map with your current location and a search bar for your destination. The app asks for location permission immediately—this is how it finds nearby drivers. Grant it, and the map centers on your position within a few seconds. The interface is clean but basic. A top bar displays the app name and a menu icon. Below that, a search bar and a "Ride" button. The bottom of the screen shows a "Delivery" option and a settings icon. The app does not ask for payment information upfront. You can request a ride without adding a card. This frictionless entry is a deliberate design choice. It lets users explore the service before committing to payment details.

The app's US origin is evident from the start. The developer address in Garland, Texas appears in the settings screen. The app is built by KROOZ, Inc., a company founded in 2015 by Godwin E Enogieru. The interface is available in multiple languages, including English, Chinese, and Hindi. The app's focus on ride-hailing and delivery reflects its target market: individuals in the US looking for affordable, reliable transportation. The app promises zero surge pricing, even during peak hours, which sets it apart from competitors like Uber and Lyft.

When the Security Code and Ride Sharing Depend on Each Other

Here is where the app's internal logic creates a critical workflow. The Safe Ride feature provides a numeric security code for each ride. The Friends and Family Follow feature lets you share your ride status with contacts. These two features are designed to work together: you receive a security code to verify your driver, and simultaneously share your ride status with loved ones. However, this creates a dependency. The security code must be entered correctly by the driver before the ride can start. If the code is not entered correctly, the ride cannot begin, which could cause delays and confusion, especially if the driver and rider are in a hurry. One user on the App Store noted that the app may use your location even when it isn't open, which can decrease battery life. This means that even if the security code works, the app may still drain your battery in the background. The app does not resolve this conflict. It presents both features as independent tools. The user is left to guess whether the security code will work smoothly or if the app will cause battery drain. This is a design flaw that could undermine the user experience. The app's success depends on reliable security features. When they work, the workflow is smooth. When they fail, the user is left with a delayed ride and a drained battery.

This dependency is not explained anywhere in the app. There is no warning that the security code may cause delays. There is no guarantee that the friends and family follow feature will work reliably. The app assumes that the security features work well together. This is a reasonable assumption for a ride-hailing app, but the evidence from the app's limited presence suggests otherwise. The app is a two-way street: you get security and sharing features, but you also get the risk of delays and battery drain. This is a trade-off that users need to be aware of.

The Reality of Daily Use: Performance, Glitches, and the Changelog

KROOZ runs smoothly on most devices when the internet connection is stable. The interface is responsive. The ride request works reliably when the network is good. The app does not consume excessive battery when idle. It only updates location when the app is open or when a ride is in progress. There are no intrusive ads. The app is free to download. The monetization likely happens through commission on rides and deliveries, not through the app itself. The app supports Android 7.0 and above, which covers a wide range of devices. The app also supports iOS 16.6 and above, which is relatively recent.

The version history shows regular updates. The latest version, 8.1, was released on June 15, 2026. The changelog states: "Minor bug fixes and improvements." This is a generic description that does not specify what bugs were fixed or what improvements were made. It leaves users guessing about the actual changes. The lack of detailed changelog is a common issue among ride-hailing apps. It makes it difficult for users to know if their specific complaints have been addressed. The developer's responsiveness to user feedback is unclear, as there are no user reviews on the Play Store. The app's update frequency suggests that the developer is actively maintaining the app. However, the generic changelog undermines trust. Users want to know what is being fixed.

Permissions, Privacy, and the Data Trade-Off

The app requests location permission to find nearby drivers. It also requests camera, contacts, phone state, and storage permissions. The data safety section on the Play Store indicates that the app does not share data with third parties and does not collect any data. However, the App Store listing for the same app indicates that data may be used to track you across apps and websites owned by other companies, and that contact info may be collected and linked to your identity. This discrepancy is a significant privacy concern. Users who value data security may want to be cautious. The app's privacy policy is available on the mykrooz.com website. The trade-off is clear: you get a free ride-hailing app, but you trade some privacy for that convenience. The app's data collection is significant compared to many other ride-hailing apps, which is a concern for users who value data security.