8 Years of IoT in Luxury Hotels — What I Learned

I spent 8 years at DigiValet building iOS apps that let hotel guests control their rooms — turn on the AC before they arrive, dim the lights for a movie, lock the door from bed. We deployed in 20+ luxury properties including Armani Hotel Dubai and Loews Hotels.

Here's what I learned.

Hardware is the wild card

Software engineers underestimate hardware. A BACnet-controlled HVAC system from 1998 doesn't behave like an API. Timeouts, protocol quirks, firmware bugs — you encounter all of it.

Rule: always assume the hardware is wrong before assuming your code is wrong.

Network reliability in hotels is terrible

Hotel networks are shared infrastructure. VLANs, firewalls, and guest isolation rules make socket connections unpredictable. We transitioned from HTTP polling to TLS sockets — a painful migration that paid off enormously in responsiveness and battery life.

UX for guests who don't read manuals

Hotel guests don't read tutorials. The app needs to be instantly understandable. We A/B tested icon designs for months. The winner: physical metaphors (a lightbulb for lights, a thermostat icon for temperature) consistently beat abstract ones.

What I'd do differently

Build a device simulator from day one. Testing against real hardware in a hotel room is expensive and slow. A faithful simulator saves weeks of debugging time.