Mobile first design

[atecey]

The new UI scales pretty well as is on mobile devices but it could work even better on mobile devices. With PWAs/Service-worker apps gaining more traction and the ability to pin them to a devices home screen as if they were native apps it would save users having to find another application to stream music to their handheld device. Though native apps do give users the ability to cache songs so not sure if this would work well with PWAs.

[jooola]

We have great apps like Dsub and similar, so I don't think we need to have "Mobile first" interface. I would be happy to be able to use it on small screens, but we will never have the real power of a real app (I'm thinking at local storage and such problems).

So we will keep this idea in mind but I don't want to prioritize small screen over computer screens. I think minimal should be something like 480 x 800.

What do you think ?

[rrrnld]

I think an interface that works well on mobile would be really nice. The way I imagine using airsonic (listening to my own music in my browser / on my phone, sharing some tracks with friends who don't care what airsonic is and just want to open a link and pretend it's spotify) definitely has a good use case for that.

I agree with @jooola on it not being a priority. I personally don't have any experience with service workers but I think nitty gritty details can still be managed very well with native apps and not-so-well with a PWA. Reacting to unplugged headphones, having buffered multiple songs, ... there are a couple of edge cases that come to mind. But a webapp that's usable for non-power-users on mobile would be very nice.