Proposing a /web directory & Web-based client (iOS/Desktop Support)

[Mr-Hasan-Hamid]

Hi everyone! 👋

I absolutely love ArchiveTune. It is by far the most premium and custom-built open-source client for YouTube Music on Android. 
Since the project is so well designed, I'd love to propose two ideas to help grow the ecosystem:

 #1. Open-Sourcing the Website (`/web` directory)
Currently, the website (https://archivetune.koiiverse.cloud) is deployed on Vercel, but its source code is not public. 
* Proposing to open-source the website code and place it under a `/web` (or `/website`) directory in the main repo.
* This allows the community to contribute enhancements, update testimonials, refine layout styles, and keep the landing page in sync with the latest releases.

# 2. Building a Web-Based Client (Browser / PWA)
Android users get an amazing experience, but iOS, macOS, Windows, and Linux users are left out. 
* Proposing to build a browser-based client (using React/Vite/Next.js) with Progressive Web App (PWA) support.
* A PWA can be installed on iOS/Desktop and integrates with system media controls (Lockscreen, media keys) via the Media Session API.
* It would reuse the same APIs (YouTube Music endpoints, SimpMusic lyrics, Last.fm, etc.) to keep the player fast and light.

What does the community/maintainers think about opening the website source and moving towards a `/web` directory structure? I'd love to hear your thoughts!

[Mr-Hasan-Hamid]

I am a web developer and would love to volunteer my time to help set up, build, and maintain these web-based parts (setting up the mono-repo structure, porting the UI to web frameworks like React/Vite or Nextjs, or refining the styling). I am happy to collaborate with the maintainers and contributors on this!