Window | نافذة

Opening the app for the first time

The moment you install and open the Window app, you are asked to either sign in or create an account. There is no guest mode. This immediately sets the tone: the app is built for residents and visitors of the Royal Commission cities who already have some relationship with the ecosystem. The login screen is clean, but it does not offer any demo or preview of what venues look like before you commit to signing up. Once you log in, the home screen displays a grid of venue categories — hotels, restaurants, and event halls. The interface is straightforward, but the lack of a tutorial or onboarding walkthrough means you are left to figure out the navigation on your own. Tapping on any category brings up a list of venues specific to the city you are in, but the app does not automatically detect your location. You have to manually select your city from a dropdown that lists Jubail, Yanbu, Ras Alkhair, and Jazan. This is a deliberate design choice, but it adds an extra step that could frustrate first-time users who expect automatic geolocation.

The initial experience is functional but not inviting. The app does what it promises on the surface: it shows you venues and lets you browse. However, the absence of any introductory guide means that users who are not familiar with the Royal Commission's booking system may feel lost. The interface uses standard Android components, so it feels familiar, but the lack of visual polish or animations makes it feel like a utility rather than a polished consumer app. For someone who just wants to book a hall for a family event, the app gets the job done, but it does not make the process feel special or easy. The real test comes when you start comparing prices and trying to book.

How price comparison and city focus work together

The app's two strongest features are its price comparison tool and its city-specific focus. On the surface, these seem separate: one helps you find the best deal, the other narrows down venues to a specific city. But in practice, they interact in a way that changes how you book. When you select a city, say Yanbu, the app filters all venues to that location. Then, when you view a venue, you see a price comparison that includes not just that venue's own rates but also similar venues in the same city. This means you are comparing apples to apples — hotels in Yanbu against other hotels in Yanbu, not against hotels in Jubail. This is useful because prices and availability vary significantly between these cities. However, the comparison tool does not factor in travel time or distance between venues within the same city, which could be a deciding factor for event planners. The app assumes that if you are in Yanbu, any venue in Yanbu is equally accessible, which is not always true. This oversight becomes apparent when you try to book a venue that is on the outskirts of the city. The app shows the price and facilities, but it does not give you any sense of how far it is from the city center or from public transport. This is a gap that users who are familiar with the area might not notice, but for visitors, it is a significant missing piece.

What makes this interaction interesting is that the price comparison feature is actually more useful because of the city focus. Without the city filter, you would be comparing venues across four different cities, which would be meaningless for someone who needs to book in a specific location. The city focus gives the comparison tool context. But the tool does not go far enough. It shows you a list of prices, but it does not show you historical price trends or seasonal variations. A venue that is cheap in January might be triple the price in June, and the app gives no indication of this. This is a limitation that users have reported in reviews, though not explicitly. The complaint about being charged without receiving a ticket suggests that the booking flow itself has issues, which may be related to how the comparison tool interacts with the payment gateway.

Real-world performance and user-reported issues

The app has a notable number of negative reviews, and they paint a consistent picture. Users report that the app charges their card but does not issue a ticket. This is a critical failure because it means the booking is not confirmed, but the money is taken. The app then shows the user as an invalid user when they try to log in again. This suggests a session management or database synchronization problem. Another common complaint is that the app lags and gives incorrect codes. This could be related to the app's backend communication with the Royal Commission's booking system. The app is not a standalone booking engine; it likely interfaces with an existing system, and any delay or error in that integration manifests as poor performance or wrong codes. The developer has released updates with "bug fixes," but the persistence of these complaints indicates that the underlying issues are not fully resolved. On the positive side, users who do manage to book successfully appreciate the convenience of comparing prices and finding venues quickly. The app's free price point is a major draw, as there is no cost to browse and compare.

The app does not display ads, which is a relief for users. There are no pop-ups or banner ads interrupting the booking flow. This is consistent with the app being a government-backed utility rather than a commercial product. However, the lack of ads also means there is less incentive for the developer to invest in a polished user experience. The app feels like a minimum viable product — it works, but just barely. The crashes and lag reported by users are likely due to memory management issues or inefficient data fetching. The app does not seem to cache venue data, so each time you open a category, it fetches fresh data from the server, which can be slow on mobile networks. This is a technical detail that users notice as lag.

Permission requirements and what they mean for your device

The app requests location permission, which is understandable given its city-specific focus. However, it does not use location to auto-detect your city; you still have to select it manually. This makes the location permission somewhat redundant. The app also requests storage permission, presumably to cache images of venues or to store booking confirmations. There is no request for camera or microphone, which is good for privacy. The storage permission is used to save booking receipts as PDFs, which is a useful feature for users who need to keep records. However, the app does not clearly explain why these permissions are needed, which could be a trust issue for users who are wary of data collection. The privacy policy, linked from the App Store, states that contact info is collected and linked to your identity, while location and user content are collected but not linked. This is a standard approach, but the lack of clarity within the app itself about data handling could deter some users. The app does not request any permissions that are out of the ordinary for a booking app, but the combination of location and storage with the reported login issues raises questions about how user data is managed. The app's permission model is straightforward, but the execution of the booking flow is where the real problems lie.