So anyway, even though the issue might not be with the app specifically, it does affect the app especially.
1 Like
OK, but clearly the interface renders differently (adaptively) to fit the different screen dimensions. I see the hamburger menu consistently on my browser because I’m using that on a desktop PC with a 16:9 screen. My phone is typically in a vertical display ratio. The interface on the phone (app) is therefore entirely different, and understandably so.
I guess what you’re saying is that for this to be resolved, and for there to be a convenient and consistent way to return to the home screen, from anywhere, that the changes would be part of the primary web app, rather than the mobile app (which based on this discussion, I’m using is simply a wrapper)?
Sorry, I was a bit behind. Several comments have clarified this. Seems we’re all on the same page 
1 Like
Wow. I just realised the app isn’t native at all. That’s impressive 
I would’ve expected hints like weird text selection or inconsistent touch response. Whatever the wrapper is, it works well
Oh, no, I achieved the annoying and sloppy text selection thing you expect from web apps, but kudos to HA and the web platform that I had to actually make an effort to do this and it’s never happened accidentally
for the frontend interface no its just a webview, everything else yes teh app deeply integrates HA with everything android like widgets, device controls, notifications, shortcuts etc…
Settings > Companion app
everything in this screen is app controlled
1 Like
Ah, OK, cool, that makes sense. No need to reinvent the wheel in terms of UI, but a native codebase to allow interaction with device services (e.g. Google Matter). Apologies for my naivety!
So… back to this. Yep. When the UI is scaled to vertical, as in the case, primarily, with the mobile app, we lose the flexibility to navigate, easily, back to the hamburger menu, and it seems it would add huge value to retain this. I guess over to the main UI forum 