Aaah, the irony. Years of “where is the official Android app?” and now here I am having to defend why there will be an official Android app
I am not going to respond to the post about Robbie having to focus. It’s his life, his time, he can do as he pleases. And if he chooses to spend that time on building open source things that he will share with anyone, let’s not discourage him, but support him instead, please?
Most work for a mobile app that smoothly integrates with Home Assistant is actually done inside Home Assistant itself: secure token based authentication, webhooks to send data back, mobile app component to tightly integrate the data with other parts of Home Assistant. Robbie has recently put a lot of work in the mobile app part, and so in proxy, Robbie is making all other apps better, including Ariela.
About Ariela. We have talked to @Ionut and looked at Ariela and decided that it does things that we would not consider suitable for an official app.
We don’t want a native UI that is built around the Lovelace config. This is not a publicly supported format and by putting it in an official app, it would be one. The customizability of Lovelace does not translate easily to native controls, and it will be an endless catch up game until you have basically reinvented the browser rendering engine?
Putting MQTT credentials on a phone means it can bypass the permission system that we’re building, by sending to topics and influence Home Assistant directly.
I don’t expect Ariela to remove features, remove ads and become open source to become an official app. That doesn’t make sense. We have been putting a lot of effort in making Home Assistant simple and easy to use, and we will continue to do so. This is not a disconnect between developers and users, ease of use is the most frequent feedback.
Having multiple apps is not a bad thing, it’s the contrary. The great thing is that if people use one app, feel that it lacks features or disagree with choices that are made, they can switch! Yay for choice.