l'archipel +

Opening the app and finding a building map that shows your exact location

The second you open l'archipel +, the app does not waste time with a lengthy splash screen. It drops you directly into a map view of the building. The map uses BOS technology to show your current position. You see meeting rooms, gyms, concierge desks, and even the marketplace. The interface is clean. Everything is labeled in French. The app assumes you know what you are looking for. There is no tutorial. You have to tap around to figure out what each icon does. This is efficient for regular users. For new employees, it is a learning curve. You might spend the first minute just zooming in and out of the map.

The map is the central hub. From here, you can book a meeting room. You tap the room, select a time, and confirm. The system updates the availability in real time. It also sends a notification to your email. The same process works for gym access. You book a time slot, and the app generates a QR code. You scan the code at the gym entrance. This removes the need for physical keys or cards. It is a frictionless experience. But it also means you are locked into the app's ecosystem. If the app crashes, you cannot access the gym. The developer acknowledges this risk in the privacy policy, but does not provide an offline fallback.

The incident reporting feature is integrated into the map. You see a red pin on the map. You tap it to report an issue. The app asks for a description and a photo. You can also report incidents from the main menu. The report goes directly to the facilities team. They receive a notification with your location and the issue details. The system tracks the status of your report. You can see if it is pending, in progress, or resolved. This is a clear improvement over email or phone calls. It centralizes all requests in one place.

How BOS technology and manual incident reporting create an information gap

The BOS technology is supposed to provide real-time building data. It monitors everything from temperature to occupancy. The app displays this data on the map. You can see which rooms are occupied and which are free. This is useful for booking. But the incident reporting feature relies on manual input. You have to see an issue and report it yourself. The BOS system does not automatically detect problems. It does not alert you when a projector is broken. It does not notify you when a coffee machine is out of order. You have to discover these issues and report them. This creates a gap. The building has sensors, but the app does not use them for proactive alerts.

This gap is not documented anywhere. The Play Store description says "manage and monitor building updates and your incident and operation requests in real time." It implies that the app is monitoring everything. In practice, it is only monitoring what users report. The BOS technology is a backend system. It feeds data to the app, but the app does not act on that data automatically. It is a one-way street. Data flows from the building to the app. But the app does not send commands back to the building. You cannot adjust the temperature from the app. You cannot turn off lights. The app is a dashboard, not a control panel. This limitation is significant for a "smart building" app.

The marketplace feature adds another layer. You can order services and products through the app. This includes catering, cleaning, and even office supplies. The orders go to the concierge team. They fulfill them manually. The app tracks the order status. You get a notification when it is ready. This is a convenience. But it also creates a dependency. If the concierge team is busy, your order is delayed. The app cannot speed up the process. It simply shows the status. The BOS technology does not optimize the workflow. It does not predict demand or allocate resources. The app is a passive tool, not an active manager.

The real-world performance: bugs, data loss, and the elusive stability update

The app has a persistent bug problem. One user reported that the app "has a habit of wiping out all your reservations and history over nightly updates without any notice." This is a serious issue. You lose your booking history. You lose your incident reports. You lose your marketplace orders. The app does not back up this data locally. It relies on the server. But the server does not seem to retain historical data. The developer has not addressed this in any changelog. The version history only says "Feature improvements and bugs fixes." This is a generic phrase. It does not specify which bugs were fixed. Users are left guessing.

The app also crashes on some devices. The App Store page lists "Diagnostics" as data collected but not linked to you. This suggests the developer is aware of crash issues. But they do not communicate fixes. The changelog does not mention crash resolutions. The lack of transparency is frustrating. Users do not know if their issues are being addressed. The developer's response to reviews is limited. They do not engage with users publicly. This creates a trust gap. Users feel like they are reporting issues into a void.

The app's performance on older devices is also a concern. The minimum requirement is iOS 15.5 or later. This excludes many older iPhones. The Android version requires Android 9.0 or later. This is a relatively high bar. The app uses high-resolution maps and real-time data. This requires processing power. On older devices, the app lags. The map takes time to load. The booking process is slow. The developer has not optimized the app for older hardware. They have not released any performance-specific updates. The changelog is silent on this issue.

The QR code generation for gym access uses a time-sensitive token that expires after 15 minutes

The gym access feature relies on QR codes. You book a time slot through the app. The app generates a QR code. This code is unique to your booking. It is also time-sensitive. The code expires after 15 minutes. This is a security measure. It prevents unauthorized access. But it also creates a practical problem. If you arrive at the gym and the code has expired, you cannot get in. You have to rebook or contact the concierge. The app does not warn you about the expiration. It does not send a reminder. You have to remember the time limit yourself. This is a friction point.

The QR code system also requires an internet connection. The app generates the code online. If you are offline, you cannot get a code. This is a problem in basements or areas with poor connectivity. The app does not offer an offline fallback. You cannot store the code locally. You cannot access the gym without a connection. This limits the app's usefulness in real-world scenarios. The developer has not addressed this in any update. The app's reliance on connectivity is a clear design limitation.