Webview like browser

[bensmithgb53]

Hi first of all great great UI.

Instead of getting links with m3u8 urls use a webview like a browser inside the app so this will be better then getting m3u8 urls directly as websites change their m3u8s a lot.

Also would be good for the Android TV app.

App features:

When a user selects a movie, it should open an information page that shows the title, description, rating, and images. (Which you already have)
After that, a splash screen should appear asking the user to pick a streaming source. The sources to show are: player.videasy.net,
vidlink.pro,
player.autoembed.cc,
vidfast.pro.

After selecting a source, the app should open a full-screen WebView inside the app to play the movie using the selected source. For TV shows, it should also open an information page with the title, overview, rating, poster, backdrop, and a list of seasons. When a season is selected, it should show all episodes in that season along with episode images. When an episode is clicked, the app should show the same splash screen asking the user to pick a streaming source. After choosing a source, a full-screen WebView should open and stream the selected episode. The video URLs should be based on the content type. For movies, use:

https://player.videasy.net/movie/{id}, https://vidlink.pro/movie/{id}, https://player.autoembed.cc/embed/movie/{id}, and https://vidfast.pro/movie/{id}. For TV shows, use: https://player.videasy.net/tv/{id}/{season}/{episode}, https://vidlink.pro/tv/{id}/{season}/{episode}, https://player.autoembed.cc/embed/tv/{id}/{season}/{episode}, and https://vidfast.pro/tv/{id}/{season}/{episode}.

This would make app great and you would only need to add new sources and not keep working out how m3u8 URLs are made. You could also add sports with this too as this is mostly easier with WebView.

Also unlimited scrolling function and filters/genre picks

Looks forward for your response. Great work 👏

[kodify-js]

Hi, thank you so much for the thoughtful feedback and kind words about the UI — really appreciate it! 🙌

You're absolutely right — using WebView for playback does simplify things significantly, especially considering how often m3u8 URLs and their structures change across different sources. It also makes it much easier to support a wider range of streaming options, including sports content, without having to continually update parsing logic.

That said, using WebView as the player does impact the app’s UI consistency and user experience to some extent, since each source has its own player interface. However, the trade-off is faster implementation and easier long-term maintenance.

What we can do is introduce an option in the app settings or during playback for users to choose between the integrated player or a WebView-based player. This way, users can pick what works best for them. If the majority of users prefer the WebView route, we’ll strongly consider shifting to it entirely.

I’ll also start working on filter options for search and infinite scrolling as you suggested — these will definitely improve usability.

Thanks again for taking the time to share your thoughts.