You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is a minor suggestion, and it's easy to implement in the demo apps. I propose adding an image (like a banner) when using Media3's audio stream instead of displaying a black screen. This visual cue would help ordinary users understand that the audio is playing even though they see a black screen, making the Media3 demo apps more visually appealing.
To reproduce the issue, simply try using any audio stream with a demo app, such as this one:
Just to give you some hint, it seems although usesCleartextTraffic has been set in Application mode, but it won't apple to MP3 URL http. especially when Mp3 http is redirected.
Cheers!
Pooya M
Banners are typically used to provide additional information or context about media content. If the media doesn't inherently include this information, adding a banner could confuse users or misrepresent the content.
The primary goal for demo apps in Media3 is to provide common use cases, which serves as starting point for developers to integrate the library into their own app. Please feel free to add your customizations as you see fit.
Hi there,
First of all, keep up the great work on [Media3]!
This is a minor suggestion, and it's easy to implement in the demo apps. I propose adding an image (like a banner) when using Media3's audio stream instead of displaying a black screen. This visual cue would help ordinary users understand that the audio is playing even though they see a black screen, making the Media3 demo apps more visually appealing.
To reproduce the issue, simply try using any audio stream with a demo app, such as this one:
https://sarcheshmeh2-ssl.icdndhcp.com/stream
With the latest Media3 1.3.0 demo apps, you'll see a black screen while the audio plays in the background.
Thanks in advance for considering this suggestion!
Pooya
The text was updated successfully, but these errors were encountered: