Thriwe–Benefits Platform

What happens when you first open the Thriwe app

Install the app, open it, and you are greeted with a login screen. No guest mode. No preview. You need a registered mobile number or an enterprise login to see anything inside. The app does not show you what benefits are available until you are authenticated. This is the first signal that Thriwe is built for businesses first, individuals second. The interface is clean but sparse — a few tabs, a profile section, and a rewards catalogue that only populates after login. The app does not offer a tour or tutorial. It assumes you already know why you are here. For individual users who downloaded the app hoping to browse available discounts, this creates immediate friction. You cannot see the value proposition without first committing to registration.

Once logged in, the home screen displays a grid of available benefits. These vary based on the enterprise partner that provided your access. A user from HSBC might see golf and travel perks. A user from a corporate wellness program might see gym and healthcare options. The app tailors the catalogue to the specific program associated with your login. This means two users opening the same app on the same day can see completely different interfaces. The app does not explain this variation upfront, which can confuse new users who expected a uniform experience.

How the B2B and B2C sides of the app pull in opposite directions

The app serves two distinct audiences: businesses that buy benefits packages for their customers, and individuals who access those benefits directly. These two use cases create a fundamental tension in the user experience. Businesses want their customers to see a curated, branded benefits catalogue that reinforces their relationship with the enterprise. Individuals want maximum flexibility and the ability to discover new perks on their own. The app tries to serve both, but the B2B side wins. The interface is heavily branded toward the enterprise partner. The benefits available are limited to what that partner has purchased. Individual users cannot add their own benefits or explore the full Thriwe catalogue unless their enterprise partner has enabled that access.

This dual structure also affects customer support. Users who experience issues — login failures, missing benefits, unresponsive support — often do not know whether to contact Thriwe directly or their enterprise partner. The app does not clarify this distinction. In practice, users report that Thriwe support is slow to respond, and enterprise partners often redirect users back to Thriwe. This creates a support loop that leaves users frustrated. The app's help section provides basic FAQs but does not address this structural ambiguity. For a platform that markets itself as a seamless benefits solution, this gap is significant.

Real-world performance: bugs, support, and the UCare integration

The app's performance is generally stable, but user reports indicate persistent issues with login and authentication. Some users have reported being unable to log in for days, with support tickets going unanswered. The app's "Bug fixes and performance improvements" changelog suggests ongoing maintenance, but the specific fixes are never detailed. The acquisition of UCare Health in 2023 added healthcare and financial wellness features to the platform, but the integration has been bumpy. Users of the former UCare app have reported issues with the coin reward system not crediting properly, and paid subscription models that limit access to benefits. These complaints carry over to the Thriwe app, as the UCare functionality is now embedded within it. The app's data safety declaration states that no data is shared with third parties and no data is collected, which is a positive signal for privacy-conscious users.

The Saudi Arabia launch in 2026 introduced a new market with different merchant partnerships. The app now supports Arabic and offers region-specific benefits. This expansion adds complexity to the codebase, which may explain the ongoing bug fixes. The app's size — over 140 MB — is substantial for a benefits platform, suggesting it includes a significant amount of media content and partner data. Users with limited storage may find this prohibitive.

Why the app requests location and phone permissions

The Thriwe APK requests access to location and phone permissions during installation. The location permission is used to show nearby benefits — gyms, restaurants, spas, and golf courses that are geographically relevant to the user. The phone permission is required for SMS verification during login and for linking the app to the user's mobile number for enterprise authentication. Neither permission is unusual for a lifestyle benefits app. However, the app does not explain these permissions clearly during the installation process. Users who deny location permission may still access the app, but the benefits catalogue will show fewer relevant options. The app does not function without phone permission, as the login flow depends on SMS verification. This is a hard dependency that users cannot bypass. The app also requests storage permission, presumably for caching benefit images and partner content. The data safety declaration states that no data is collected or shared, which aligns with the permissions being used solely for app functionality rather than tracking or advertising.