Itβs such a small thing in the scope of what this platform does in my life, but Im super hyped for the new UI sugar added in this release.
Drag n drop is great but honestly what I want is a native UI on each platform.
I realize that they aren't reinventing the wheel with the UI updates this year so it's not really comparable/fair to say but I just want something faster and more responsive (especially on mobile). It seems crazy to me that in 2024 the fastest hardware available still takes a couple seconds to show my dashboard on a cold boot of the app.
A native ui wouldn't have much or any impact on time to show your dashboard. But it would add an astronomical overhead to the development costs
Yea, we don't really need first party native UIs (the community can do that themselves), just more control and configurability over what we currently have.
I'd like to see some better screen formatting options without having to use custom code or unofficial add-ons.
For example, I'd like to make a grid layout that auto stretches and flows for different display sizes like a modern website can, or lock to a screen width/height etc for a fixed wall mounted controller so I don't get random scrollbars on some screens.
And more control over things like tap and hold actions. it's almost impossible for me to use tap and hold on my main wall mounted display for example, if I move by a single pixel it doesn't react, I'd like to set the deadzone and delay time for that for example.
I work in mobile and respectfully disagree with it having no impact on time to show. You might not notice much difference if you are inside your house using gigabit WiFi, but go load your dashboard on a slow 3G/4G network lol
Sure, there is a higher development cost but you get what you pay for in this case. The project already supports native apps for Android, iOS and Mac.
That makes no sense. Are you are implying that somehow going native gets you faster network transmission speeds?
Besides, the dashboards in home assistant are heavily customizable with css, which means that just using native components is not practically feasible.
Are you are implying that somehow going native gets you faster network transmission speeds?
No. If the components are native they can be loaded immediately without network transmission. The network calls for the current status of entities can happen in parallel and would complete much faster than one large webpage load.
And your standard cards can not be modded with CSS unless you install something 3rd party that allows that.
The native apps are functionally webapps, they are not "native". You should be able to tell that if you "work in mobile".
What are you running home assistant on? On my pixel the app only takes ~2 seconds to open and load on 4G
Pixel Fold. It takes ~2 seconds on gigabit WiFi. Slow 4G networks take a lot longer than 2 seconds. Could be pretty much instant regardless if it was native.
I meant the host computer, raspberry pi? I was giving my phone opening time as reference, should have made that more clear.
I'm also on a pixel fold. The performance is fine for me, but I'm hosting home assistant on a VM running on a server with Ethernet to my networking switch.
Host computer is an old i7 desktop running proxmox. I don't think that's the problem.
I just think a native dashboard in the apps would be better for a bunch of reasons and the Home Assistant project is big enough now to support/warrant it.
Love it, but I'm still trying to understand why the storage it takes to operate a few ESPHome devices keeps growing and growing even though data retention is set to 7 days.
Home Assistant is open source home automation that puts local control and privacy first. Powered by a worldwide community of tinkerers and DIY enthusiasts. Perfect to run on a Raspberry Pi or a local server. Available for free at home-assistant.io