OpenApp vs legacy lobby intercom and access (HID, Doorking, Linear)

Legacy multi-tenant residential systems (HID, Doorking, Linear, and similar) often combine on-premise controllers, physical fobs, landline lobby intercoms, and local desktop software to manage tenants.

OpenApp is a virtual intercom and cloud access layer: QR, NFC, or short link at the door, building directory, native mobile call UI (CallKit / ConnectionService), guest invites, API provisioning, and audit — opening doors through integrations you choose.

Recommended approach: keep the legacy intercom and access panel as the reliable baseline, and add OpenApp as an additional layer for modern entrance management — not an overnight rip-and-replace of the lobby phone.

Virtual intercom — know the dependency

OpenApp Virtual Access is phone-first:

• Visitors use a smartphone browser (or you provide signage with QR/NFC).
• Residents answer calls and unlock through connected mobile devices with working network (cellular or Wi‑Fi).

That means:

• A resident without a charged, connected phone cannot rely on OpenApp alone for lobby calls the way they can on a landline panel wired to every unit.
• During outages (dead phone, no signal, app not installed), the legacy intercom still matters.

We advise keeping legacy lobby intercom hardware in service — at least through migration and often permanently as fallback — while OpenApp handles guest invites, delegation, API automation, and optional parallel entry paths (side doors, gates, STR units).

Layered architecture (recommended)

Lobby (primary reliability)     Legacy panel + landline / wired intercom
        +
Lobby / side entries (modern)   OpenApp portal (QR/NFC) → directory → mobile call → unlock
        +
Back-office                     OpenApp dashboard + API (invites, roles, audit, scripting)
        +
Openers                         Your integrations on strikes, gates, relays

OpenApp does not emulate Wiegand/OSDP inside the legacy controller. You add cloud-managed openers and portals alongside existing infrastructure — or on entries the legacy panel never covered (garage, package room, STR sub-entrances).

Typical rollout:

1. Mount QR/NFC signage at lobby or secondary entries (stable portal URLs) — in addition to the existing panel.
2. Link openers to strikes, gates, or relays via the integrations catalog where the legacy stack does not reach.
3. Model apartments in the Virtual Access directory; delegate residents per unit.
4. Use OpenApp for guest invites, PMS/automation hooks, and multi-site API — while the legacy panel remains for residents who prefer the familiar buzzer.
5. Retire legacy hardware only when the building explicitly accepts phone-only intercom — not as the default recommendation.

Comparison

	Legacy on-prem	OpenApp (virtual layer)
Intercom	Panel + landline / wired to unit	Signage → phone browser + CallKit / ConnectionService
Resident requirement	Desk phone or panel handset	Working, connected smartphone
Reliability profile	Works without resident mobile app	Depends on resident device + network
Tenant admin	Local PC database	Cloud dashboard + API
Guest access	Manual / fob programming	Time-bound invites
Audit	Local logs, hard to export	Dashboard review + integrator logs
Hardware at door	Vendor controller + panel	Your signage + modular openers
vs legacy	Baseline	Additional modern path — keep both

When OpenApp adds the most value (with legacy kept)

• Guest and STR access — time-bound links without reprogramming fobs
• Property-management API — provision units and residents without the local access PC
• Per-apartment delegation — unit reps manage their own invites and directory labels
• Extra entry points — gates, garages, side doors the old panel never served
• Unified org — same platform for parking, pedestrian doors, and automation elsewhere on site

When to rely on legacy only (for now)

• Life-safety or certified panel requirements mandate specific hardware
• Resident population cannot depend on smartphones for primary lobby access
• No network path to cloud-managed relays yet
• Recent capital investment in proprietary controllers — extend with OpenApp, do not force replacement

Related guides

• Virtual intercom flow
• Shared apartment building access
• OpenApp vs ButterflyMX — another virtual intercom option; same phone dependency applies
• OpenApp vs Latch