Why Haevn doesn't do smart home (and probably never will)

Every family app gets asked the same question eventually: 'Does it do smart home?' It's a reasonable question. If one app can hold the calendar, the shopping list, the budget and the school run, surely the lights and the thermostat belong in there too.

We looked at it seriously. Then we decided not to build it. This is why.

The temptation

Smart home is the most obvious 'and one more thing' any family platform can bolt on. The APIs exist. Voice assistants and dedicated smart home hubs already do the heavy lifting. Slap a tile in the app, connect a few devices, and the product looks fuller in a screenshot. It's a very tempting box to tick.

It also demos beautifully. A single dashboard where you can see the school run on the calendar and the porch light in the same view is a good picture. Every family app that has tried this has produced roughly the same demo, and roughly the same real-world result.

What we considered, and decided against

We looked at three versions of it.

• A thin integration layer. Read state from voice assistants and dedicated smart home hubs, show it inside Haevn. Low effort. Also low value, because you're still setting the devices up somewhere else and the tile in Haevn is just a mirror.
• A full control layer. Pair devices directly, run routines, handle the whole stack. High effort, high support cost, and it duplicates work that voice assistants already do adequately.
• A calendar-triggered layer. 'When the family calendar shows you're on holiday, drop the thermostat.' Genuinely useful for a slim category of household. Also fragile, because it depends on the calendar being trusted enough to drive real physical outcomes, and most family calendars aren't there yet.

Each option would have taken engineering time that we would rather spend on the things every family in our research told us were breaking: the mental load, the shared money view, the household admin, the co-parent handover. Smart home is not on that list. Not once, not in any household we spoke to.

Where smart home actually shines

To be fair to the category: smart home does earn its keep in specific places.

• Thermostats. A learning thermostat pays for itself in energy savings within a couple of years, and 'don't heat an empty house' is a real behavioural win.
• Energy monitoring. A clip-on meter or a smart plug on the tumble dryer tells you which appliance is actually costing you money. That's useful.
• Doorbell cameras. For families with older children arriving home independently, seeing who's at the door from anywhere is a small daily relief.

These are the honest wins. They are also, notably, three separate devices doing three separate jobs. They don't need a family operating system to make them work.

Where it fails families

The failure modes are consistent, and we heard them again and again.

• Platform fragmentation. Your thermostat is on one platform, your lights on another, your doorbell on a third. Getting them to talk to each other properly is a hobby, not a feature.
• Voice-first design excludes half the household. Toddlers can't voice-command anything. Older children can, and then do, at volume, at 6am. Elderly relatives often can't rely on it at all. The people who need the house to be predictable are the people the voice model serves worst.
• Physical controls still matter. Grandparents visiting, a babysitter for the evening, a partner who's had a long day: they all need a switch on the wall that does what a switch on the wall has always done. Removing that in the name of 'smart' is a downgrade.
• It solves a comfort problem, not a coordination problem. Family life breaks down over who's picking up whom, who paid for what, and which form is due Friday. Not over whether the porch light is on a schedule.

What actually reduces the mental load

The things families told us they wanted, in order, were: one shared calendar that both adults trust; a shared view of money so one person isn't the household finance manager by default; a place for the boring paperwork so it stops living in someone's head; and, for co-parents and carers, a calm way to hand information across without a WhatsApp thread as the audit trail.

That's the product we're building.

• The Plan. The shared family calendar, colour-coded per person, with the school run, the clubs, the appointments and the handovers in one view both adults trust.
• The Pot. A shared household budget view, so both partners see what's going out, what's coming in, and what the joint monthly picture actually looks like.
• The List. Shared lists that live where the rest of family life lives, not in a separate app that only one person opens.
• The House. The boring, essential admin: utility bills, renewal dates, warranties, contractor details, appliance manuals. Searchable, in one place, so neither adult is the sole keeper of the paperwork.

None of that requires a lightbulb API. All of it moves the needle on the thing families actually asked for.

Honest FAQ

Will you ever add smart home? Probably not. If a specific integration turned out to remove a real bit of household admin (something like 'the boiler tells you when the service is due so it lands on the calendar'), we would look at it as a data integration, not a control panel. We would not build a rival to the dedicated hubs.

Isn't this just admitting you can't build it? No. It is engineering time we would rather spend elsewhere, on the problems families told us are actually breaking. Building 'smart home lite' would make Haevn look fuller and work worse.

What if my family already runs on a voice assistant? Keep it. It's a different tool, doing a different job. Haevn sits alongside it, holding the calendar, the money and the admin. There is no need for the two to be the same app.

Doesn't every big platform do smart home? The big platforms have the hardware business to defend. We don't. That's a feature of being smaller, not a limitation.

The one-line version

We looked at smart home for families and decided the household coordination problem is a bigger, more painful, more under-served problem than the 'is the porch light on' problem. So we're solving the first one properly instead of solving the second one badly.

Start your free 14-day trial. 14 days free, no card required.