search

andrewrk / groovebasin

Music player server with a web-based user interface.
MIT License
1.9k stars 119 forks source link

Mobile friendly UI #365

Open SCastaneda opened 10 years ago

SCastaneda commented 10 years ago

Are there any plans of making the UI mobile friendly? Just being able to selecting and start already uploaded songs would be great.

malakada commented 10 years ago

Here's where I've started on that:

https://github.com/melissanoelle/groovebasin/tree/feature/new_ui

Once that's done, I plan on opening a second branch to add in actual mobile interactions that are expected in a narrower viewport.

rchrd2 commented 9 years ago

:+1: Mobile UI would be great

mrdomino commented 8 years ago

++

paulproteus commented 8 years ago

Whoa, super cool that @melissanoelle worked on a mobile-oriented UI!

Whoa, and a native Android app: https://github.com/melissanoelle/groovebasin-android !

I'm curious @melissanoelle if you're interested in continuing work on that. If not, that's life; it's probably useful to indicate here to encourage others to work up the enthusiasm to work on it. If you are, then that's even cooler.

paulproteus commented 8 years ago

My interest in this, for what it's worth, is I'm a participant in @mrdomino 's groovebasin instance, and would enthusiastically use an Android app or mobile-optimized web UI, as I have an Android phone.

malakada commented 8 years ago

Mmmmm.

I decided I wanted to learn Android dev so I picked it up as a project when I was an active user of groovebasin's web client. My Android skills haven't been used since then, so it would be a large time investment for to pick it back up right now. If other devs who knew what they were doing (or at least enough to know how to work on the project) became active on my repo there, I'd enjoy helping out implementing the UI. I was strongest in that area, so I feel like I could still help with that. :)

I was also working on a mobile-optimized web UI at one point, and I've got a branch somewhere but the amount of DOM changes that need to be made to really do it right created so many changes that the branch just grew too large to really manage properly... and I didn't really believe that @andrewrk would have any interest in merging it in anyway. If you go the web UI route, my start is here: https://github.com/melissanoelle/groovebasin/tree/feature/new_ui