There is a music streaming platform, which is supposed to only let registered users to play and download musics from it. On the desktop view of web app, as expected you can only see available playlists but no play button. So you have to register or log in, buy a subscription and then play or download a playlist.
One of steps in testing a web app, is to check the mobile view of it. There are multiple ways to test that. The simplest is to make your browser window small, so according to viewable pixels the front end of the web app changes to the mobile mode. Some apps like this target have different views for different devices and viewable pixels. So we could now see the musics in the playlist, and *click* we can play the musics in playlist.
We still couldn't download it via the app, this one was hard coded for the users with subscriptions. But there was a way to save the musics which you can read here ==[[2026-05-03-WebApp-MobileView-SaveMusics-DRAFT]] VIP== .

As I said, we could turn to mobile view just by making our browser window smaller (vertical) to get a mobile view. But some apps identify mobile devices using different methods. So if that didn't work, you can change your user agent string to an exact IOS or Android browser user agent. If that is hard, use your browser's developer options / debugger to apply mobile view based on mobile device models (This can be different on different browsers, so I recommend to google it based on what you use). These 3 methods must work, but if you face a different scenario, I recommend you to check the HTTP headers too (These can lead to the backend but can be useful).

I hope this comes in useful for ya.