Home Assistant dropped a “beta 1.0” label, and I wanted to talk through what 1.0 even means when the project isn’t a typical piece of software. This isn’t Spotify or Discord with a small team and a fixed “done” milestone—Home Assistant is a platform built by a huge open-source community with thousands of contributors across core, frontend, docs, and integrations. So when people see “1.0,” they assume “finished,” but for a constantly-growing smart home platform, “finished” is a weird concept. My ideal Home Assistant 1.0 is mostly about usability: I should be able to hand it to my parents or grandparents and have it be easy to install, easy to navigate, and basically self-explanatory. No YAML. No digging through docs just to build a dashboard card or a simple automation. I want guided UI with sane defaults, better generated dashboards, and a more “template/marketplace” feel—think Supervisor/add-ons, but expanded to dashboards, automations, and scripts. On the stability side, I talk about breaking changes and release cadence. I’d love to see clearer “stability tiers” for integrations (a rating-style system) and more staged releases so people who want rock-solid reliability aren’t forced into weekly churn. The big reality check: 1.0 is hard because Home Assistant depends on tons of external APIs and devices that companies can change or kill at any time—even “local” APIs can disappear after a firmware update.