-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
player UI is abysmal #2
Comments
Thanks a bunch for your comments! I've been playing around with different UI ideas for the player, the main restriction always seems to be space.
|
On Sun, Sep 22, 2013 at 11:48:38PM -0700, Colin Frei wrote:
I agree. I have added the first step more in order to make the
I was thinking even for resuming individual tracks in the last place. If And yes, meanwhile, I would vote for "play the last track you played"
Hmm, and wouldn't be just the most simple way (which is most often than
OK, but this I would definitively classify as "Simplification of UI by Matěj |
Added a progress line to cover point 3 |
Thinking about it, I came to the conclusion that the only real solution how to press all those requirements into given space of phone, is just to do the same what for example Podax did: add new special page which would work solely as player. If you want to crammer all the player functionality in the queue page, I think you get only something subpar. Just my €0.02 |
Let’s put here some screenshots of Podax:
|
Thanks alot for your detailed feedback! |
I have created my own fork of Podcast so I have imported my own OPML file (yes, forking of the repo is probably not a good end-user UI ;))
It seems like whole app works reasonably well. Except for the player UI.
Podcast player UI should have these functionality:
I believe that the best solution for this moment is using a regular HTML element (perhaps with some CSS embellishments)
The text was updated successfully, but these errors were encountered: