DOOR: Smart Access & Control

Getting In: The First 30 Seconds of Using DOOR

Opening the DOOR app for the first time triggers a permission request for Bluetooth. That is the first hurdle. Without granting Bluetooth, the app cannot unlock any door—doorcodes and keycards still work at the lock, but the phone-based unlock simply will not function. The setup flow then asks for location access and pushes you toward creating an account or migrating from the older Latch app. This migration path is a critical point: Latch users are told to download DOOR and log in with their existing credentials, but many report that smart home devices like ecobee thermostats go offline after the transition. The onboarding experience is not a smooth welcome screen; it is a series of functional gates that determine whether the app will actually work for you. Once past these gates, the home screen displays four main areas: Home, Access, Devices, and Services. The Access tab is where your doors live. If no doors appear, you are either not in a DOOR-enabled building or your property manager has not added you yet. That is a common frustration point—the app itself cannot fix that; it depends entirely on the building's backend configuration.

The DOOR app is free to download, but its utility is entirely tied to the physical infrastructure of your building. It is not a standalone smart lock controller for any door; it only works with DOOR-compatible hardware installed by the property. This makes the app a mandatory tool for residents but also a captive one—you cannot switch to a competitor if the building uses DOOR. The app's core loop is simple: open the Access tab, tap your door, and wait for the Bluetooth handshake. That handshake is the moment of truth. It works reliably for some users and fails unpredictably for others, often requiring the phone to be within two feet of the lock. The app does not offer a remote unlock over the internet; everything is proximity-based. This is a deliberate design choice for security, but it also means you cannot let someone in from across town unless you share a doorcode, which is a separate feature that works independently of Bluetooth.

When Bluetooth and Doorcodes Collide: A Workflow Analysis

The DOOR app offers two primary unlock methods: Bluetooth proximity and a 4-digit doorcode. These two features are designed to work in parallel, but in practice they create a confusing interaction. A resident can unlock with Bluetooth by simply being near the door and tapping the unlock button in the app. A guest, however, receives a doorcode via text or email. The doorcode works by entering the digits on the Latch Lens keypad at the door. The confusion arises when a resident is also trying to use Bluetooth while a guest is entering a code—the system can get out of sync. Some users report that the app shows "Out of Schedule" errors even when the doorcode works, or that Bluetooth unlock fails because the app is still trying to process a code-based request from a previous attempt. This is not a bug per se; it is a consequence of two separate authentication pathways that do not always communicate cleanly with each other. The app's support documentation acknowledges this: it recommends performing a manual door sync if you see an "Out of Schedule" error, which forces the app to re-fetch the current access schedule from the cloud. That sync process takes a few seconds, but during that time the door remains locked. For a user carrying groceries in the rain, those seconds feel like minutes. This interaction between Bluetooth and doorcodes is not described on the Play Store page—it is an emergent behavior that only becomes apparent through repeated use.

The app also includes a widget for iOS that promises quick unlock from the home screen. However, multiple reviews indicate that the widget often fails to work, especially when the phone is locked or when the app is not running in the background. The widget attempts to use Bluetooth, but if the app has been force-quit or if Bluetooth permissions have been revoked, the widget simply spins and times out. This is another example of how two features—widget and Bluetooth unlock—interact poorly. The widget is meant to be a shortcut, but it often becomes a source of frustration because it does not gracefully handle the underlying permission and connectivity requirements.

The Reality of Living with DOOR: Bugs, Crashes, and Unresponsive Support

The most common complaints about DOOR are not about missing features but about reliability. Users report that the app logs them out regularly, often at the worst possible moment—when they are standing outside their building with their hands full. Re-logging in requires a data connection, which is not always available in underground parking garages or elevators. Once logged back in, the app sometimes takes 15 seconds or more to re-sync and show the unlock button. This delay is not just an inconvenience; it can be a genuine safety issue if you are trying to get inside quickly. The app's performance on Android appears to be particularly inconsistent. Some users say it works "half the time," while others report that the entire door lock system is "very buggy." The transition from Latch to DOOR seems to have exacerbated these issues for existing users, as the new app replaced the old one without a seamless migration path for smart home devices. Thermostats, leak detectors, and other DOOR Smart Home devices that worked under Latch often stopped reporting or became unresponsive after the switch. The official support documentation provides troubleshooting steps for many of these issues—power-cycling devices, checking WiFi, syncing manually—but these are workarounds, not fixes. The underlying problem is that the app's backend integration with smart home devices is fragile.

Customer support is another sore point. Several reviews mention that emails to support go unanswered, and there is no live chat or phone number for residents to call. The support site is comprehensive in terms of documentation, but it is self-service only. If a hardware issue arises—like a deadbolt jamming or a keycard reader not working—the resident has no direct escalation path within the app. The property manager is the intermediary, which adds another layer of delay. This is a structural limitation of the DOOR ecosystem: the app is a tool for residents, but the property manager controls the backend. If the property manager is slow to respond, the resident is stuck.

The Bluetooth Permission Lock

The DOOR app requires Bluetooth permission to unlock any door via phone. Without it, the app cannot complete the handshake with the lock. This is stated clearly in the support documentation. However, the app does not always handle permission denial gracefully. If a user denies Bluetooth permission during the initial setup, the app still loads and shows the Access tab, but the unlock button is either grayed out or simply does nothing when tapped. There is no in-app prompt to re-enable permissions; the user must go to the system settings manually. This is a small but significant design flaw that catches new users off guard. The app also requests location permission, which is tied to Bluetooth scanning on Android. Without location permission, Bluetooth scanning may not work reliably, even if Bluetooth itself is enabled. This chain of dependencies—Bluetooth plus location—creates a barrier to entry that is not obvious from the Play Store description. The app does not explain these requirements during onboarding; it simply asks for permissions and moves on. For a user who is not technically inclined, the app may appear broken when it is actually just missing a permission. This is the final, abrupt reality of using DOOR: it works only when every permission, every sync, and every backend configuration aligns perfectly. Any deviation, and the door stays locked.