I hope it’s not april fools, as already HTML5 notifications on androidstart to suck…
I hope one of the first features would be it and coords reporting. Rest can be (at 1st release) just lovelace-webview.

BUT I’m afraid spreading your focus on EVERYTHING will probably hurt quality and growth of the iOS app.

Competition is great when it comes to Android vs. iOS vision difference as every side can get inspiration (like cams, tre/hum sensors on Android and native integrations on iOS), but not inside one platform when the official status of the app kills innovation and already invested efforts.

I believe the better way is to overcome obscure frictions with Ariela developer @Ionut.

Paulus have opened up for the existing android apps to become official, but apparently that doesn’t seem to be something they want. On the latest podcast he explained what is needed of app devs to make an app official. There need to be an official app.

Hi there, actually even few days ago i made the proposal of making Ariela open source in order to became the official Android app for Home Assistant, proposal which was rejected for a couple of reasons. Still, the idea of having an official Android app is a very best one, and if i can and if i am allowed i will like to contribute to the new application and of course support and add new features to Ariela. Having multiple apps to choose from will allow users to have best Home Assistant experience based on their needs, users being what it matters for me and i suppose for the team behind Home Assistant.

Ariela tend to have native implementation for the UI, and a web based UI is preferred

The application do not use the new mobile_app component yet

Ariela makes wrong assumption about the way users needs to use the authentication (they always need to use the web login)

Anyway, like i said before, there is no reason multiple apps couldn’t coexists for Android users. At the end users will choose the best app that suit their needs in order to have best Home Assistant experience. And of course if i can i will going to support the new official android app.

Robbie will be THRILLED to have someone else assisting him with this app. His biggest problem with the iOS app was doing everything himself and not having any help. He would welcome your assistance with both arms…

In regards to the items mentioned of why it was rejected, would it not be possible to overcome them so that it could become the official app, that way yourself and robbie have a good base to start with?

I’ve tested most of the current Android apps.
With every each of them I have issues either regarding visual side or vision for development.

I’ve just looked up HA App in Apple Store (as I don’t own apple device) - and it’s exactly what I would require from app! It supports GPS, notifications and pure webview.
I like my lovelace UI, why does all the devs try to do anything with that…

I hope to see just an clone from iOS on Android and called ‘official’ so it’s always up to date with the API and growing with HA.

If “official” Android app implies it must be open-source then that narrows the field of available options.

The inherent risk of elevating a closed-source app to “official” status is the app’s developer may ‘go dark’ (looking at you Zanzito). Without access to the developer or the source code, the community has no ability to update it and must find another “official” app.

An open-source app may be chosen as the official one but that doesn’t necessarily eliminate the market for a paid, closed-source app that offers superior functionality and performance. Competition breeds innovation and users will be drawn to whatever serves them best.