Hospitality UI vs. residential UI — design choices that differ.

The shared starting point: both Tahoe and Altitude are written natively in Crestron CH5 on current-generation TSW and TS panels. The design discipline is the same — typography drawn against the architecture, palette pulled from the materials, motion tuned to the panel’s actual response, scene language composed by hand. The toolchain, the firm voice, the engineering rigour are constant. What changes when the surface moves from a residence to a luxury hotel is the operational brief, and the operational brief reshapes almost every composition decision the residential version takes for granted.

Brand on the panel.

A residence’s panel carries the household’s identity — the architect’s typography, the interior designer’s palette, the principal’s preferences. The brand is, in the technical sense, the residence’s. Households at the top of the market often have a typography system they’ve developed across several residences; the panel sits inside that system.

A hotel’s panel carries the property’s brand — and the property’s brand is a more formalised system than a household’s. There are brand guidelines that govern typography, palette, logo treatment, motion, voice. Print collateral, digital surfaces, signage, in-room books all share the same system. The panel sits inside that system the same way a printed welcome card does.

The work for the design firm is materially different. On a residence we’re composing the panel with the architect and interior designer; the panel is one of several finishes decisions that happen alongside one another. On a hotel we’re composing the panel against an existing brand book that’s been refined over years and is not negotiable in the way an in-progress residential palette is. The hotel’s creative director has authority over the brand expression on the panel; we’re the engineering hand that makes the panel render the brand correctly on a Crestron surface.

Multi-user by default.

A residential panel is composed for the rhythm of one household. Morning compositions surface when the household tends to wake; evening compositions surface when they tend to settle. The panel learns the household and refines around them; the household learns the panel and trusts it. One vocabulary; one rhythm.

A hospitality panel is composed for the rhythm of arrivals, turn-downs, room-service deliveries, housekeeping cycles, the events the property runs, and the dozens of guests who pass through each room over a season. The composition can’t learn a specific household because there isn’t one. Instead the composition is set against the property’s operational pattern — standard guest behaviours, expected staff behaviours, and the events that aren’t standard.

This leads to a structural design decision residential UI doesn’t face: separating the guest-facing surface from the staff-facing surface. The guest sees a calm panel with one vocabulary; the staff sees a different panel (often physically the same device, but a different composition triggered by a service mode) with a different vocabulary, more controls, and the ability to override anything the guest has set. The two surfaces share the same underlying scene engine but read as different products.

Integration with hotel systems.

A residence’s technology stack is mostly self-contained — Crestron, Lutron, the IoT layer, maybe a building-management system for serious mechanical plant. The household-facing surface speaks to the underlying scene engine and that’s the boundary of what it integrates with.

A hotel’s technology stack is significantly more interconnected. The property-management system (PMS — Opera, Mews, others) tracks reservations, room state, guest preferences. The building-management system runs the mechanical plant. The guest-experience platform tracks loyalty, room amenities, in-stay messaging. The point-of-sale system runs F&B. The lock system controls room access. Each of these is a separate vendor with its own API surface; the Crestron scene engine has to read from all of them and contribute back to several.

On Altitude, we coordinate that integration during design development. The hotel’s existing systems are an input to the panel composition; the panel becomes a surface where the guest’s preferences (from PMS) shape the room’s default scene, the mechanical state (from BMS) is reflected in the climate setpoint, the messaging surface lets the guest speak to the property without picking up a phone. Each of those integration points is a programming decision; none of them are decisions a residential UI needs to make.

Repeatability at scale.

A residence typically has one or two panel compositions — the in-wall panel in the main living spaces, sometimes a different composition for the master suite. A boutique luxury hotel has dozens of guest rooms, several suite tiers, F&B venues, conference rooms, back-of-house surfaces, perhaps a spa or a club. Each surface needs a composition; each composition needs to read as part of the same property.

This produces a different design approach. On a residence, every composition is one-off; on a hotel, the composition is a system — a base composition for each room type that propagates to every room of that type, with carefully chosen variation points (the suite that overlooks a different view; the corner room with different exposure). The work the design firm does is closer to building a small design language than to composing a single surface. The deliverable is a system of compositions, not a fixed set.

The benefit of doing this work properly up front is operational. A hotel adding a new room tier two years after opening doesn’t need a fresh design engagement; the new tier inherits the system, with variations specified to the level the property warrants. A hotel renovating a wing doesn’t face a panel redesign; the existing system absorbs the new wing through its variation rules.

The guest experience.

A composed hospitality panel reads the way the rest of the room reads. At the right moment after check-in, the climate is at the guest’s preferred setpoint (read from PMS); the lights are at the scene the property has chosen for arrival; the shades are at the angle the property has chosen for that time of day. The panel doesn’t announce itself with a welcome screen; the room has already done the welcoming.

The guest interacts with the panel only when they want to change something the room has already set up for them. Lift the shades; soften the lights; raise the temperature. Three taps maximum for the things a guest does daily. The complex controls — deep climate adjustments, audio routing, voice surface choices — sit two layers down for the guests who go looking; out of sight for the ones who don’t.

The panel is not how the property markets itself. The property markets through architecture, through service, through the in-room book, through the brand. The panel is one fixture in that ecosystem; its job is to disappear into the room the way a switchplate does.

The operator experience.

The staff-facing surface is a different animal. Housekeeping needs to know which rooms are turned, which need service, which have do-not-disturb on. Engineering needs to see climate anomalies across the property in one view. F&B needs to coordinate banquet-room presets. The staff-facing composition is more functional, more dense, more keyed to operational language than the guest-facing one.

Where the panel is physically the same device (a TSW in a guest room with a service mode), we compose two surfaces: one calm for the guest, one functional for the engineering tech holding a service key. Where the surface is dedicated staff hardware (a panel in housekeeping, a console in the back office), we compose for the operational vocabulary specifically — less attention to typography and motion, more attention to information density and keyboard shortcuts.

On a hotel-wide scale, the operator-facing surfaces often integrate with Intuitiv AI for property-intelligence functions — one inbox for the engineering manager, ranked findings across rooms, plain-English service notes. The same architecture we deploy for AV integrators serving multi-residence households serves hospitality engineering teams managing a single property at scale.

When a property is hybrid.

Some properties carry both residential and commercial portions in the same building — private residences inside a hotel, members-only apartments above a club, a flagship suite that’s leased annually rather than nightly. The design challenge in those properties is more layered: the residence portion warrants a residential composition (Tahoe), the hotel portion warrants a hospitality composition (Altitude), and the two compositions need to read as part of the same property without merging.

In practice we compose this as a design system with two distinct vocabularies that share a brand language. Both speak in the property’s typography and palette; both feel like part of the same building. The vocabularies diverge at the operational level — the residence’s scene language is for one household; the hotel’s scene language is for many guests. A resident moving from her apartment to a meal in the hotel’s restaurant should sense that she’s in the same property; the operational machinery underneath is configured differently.

Closing.

Tahoe and Altitude come out of the same studio with the same engineering rigour. The visible decisions diverge because the operational briefs diverge. Brand on the panel. Multi-user surfaces. Hotel-systems integration. Repeatability at scale. The guest-versus-operator separation. The hybrid property design problem. Each is its own design conversation; none of them apply to a residential UI.

If you’re a hospitality operator evaluating a panel-design partner for a luxury property — or if you’re an architect or interior designer on a hospitality project trying to understand what changes when the surface is commercial — we’re glad to read the brief and write a short recommendation. The shape of the engagement is described in detail on the Altitude page.