Proposal: Android hosted-library connection, phone layout, and desktop HTTPS

[keodime]

I’d like to check the scope with maintainers before implementing features.

• Connect to a hosted library from Android. The desktop-hosted library opens in Chrome, but connecting from the Android shell fails in my setup. I reproduced a 403 by sending a request with the shell’s loopback origin. Would a native connection option that loads the selected hosted IPTVnator page directly in the WebView fit the project? It would reuse the existing sign-in flow and keep the server’s origin checks.
• Make the phone layout readable. On a phone the shell scales down its TV viewport, which makes text and controls small. I’d propose a responsive touch layout for phones and tablets, with separate checks for D-pad navigation and the existing Android TV and Fire TV layouts.
• Support remote access to desktop hosting. Separately, I’d propose opt-in HTTPS behind a trusted reverse proxy for Windows, macOS, and Linux, with the same URL usable in a browser and in the APK. Would you prefer generic HTTPS support first, or would you also welcome optional Cloudflare Tunnel setup in the app? I’d like to check whether bundling an optional connector fits your packaging and maintenance expectations. We would keep http self-hosted options.

This just an idea.

I’d split these into separate PRs and start with the Android connection. Does that direction fit the project, and are there related changes you’d like me to coordinate with first?

[4gray]

Thanks for the proposals, happy to review contributions in this direction.
1-2. Sounds good.
3. Let’s start with opt-in HTTPS behind a user-managed reverse proxy and revisit built-in Cloudflare Tunnel support later.