GNOME Bugzilla – Bug 634107
Feedback is very subtle when adding podcasts from Miro and therefore easy to miss
Last modified: 2020-03-17 08:54:34 UTC
I keep wondering if I actually managed to add a podcast from Miro or not, or if it didn't work. Ivanka seems to have this problem too (will add her to cc).
Yeah, it is pretty subtle. Have any suggestions for improving it?
Dude, you are sooo fast when it comes to reply to my bug reports! Ivanka sent me an e-mail with some suggestions, I've asked her to post them to this bug, but since this bug is on a fast pace, I'll copy+paste directly out of her e-mail: " Anything would do: - a notification [1] - a notification bar at the bottom - something else that I can't think of right now " 1. Ivanka: do you mean using the systems notification system?
It seesm Miro is using the notification system. It says something along the line of "Subscribed to new feed http://url-too-feed-goes-here" Not sure if that is too annoying or not.
Miro as in "Miro Player" of course.
It seems weird to use the system notifications to alert the user to something happening in the app they're in (and caused directly by them). It's for basically that reason we don't show song-change notifications when Banshee is focused.
Indeed. Maybe a bar sliding in an out inside the application? I'll try to figure out some other alternatives as well.
One idea is to do something similar to our "user job" progress bars, that pop up beneath the source list when a podcast is downloading, or your DAP is syncing.
Created attachment 174033 [details] Screenshot showing the bar I think we mean
Hi guys, I just added a screenshot which shows the bar I think you mean. If you mean the bar which says: "disconnecting media player" then sure - that would be absolutely fine. Feedback is a very important part of creating the right user experience and - while I understand that system notifications might seem like overkill - it needs to be clear and obvious enough to reassure users that what they wanted to happen did happen. Anyway - now I have found where to file the bugs I shall report my own directly! Ivanka P.S. Thank you to the creator of the 'emusic plugin maker(s)' - am making very good use of that!
Created attachment 174034 [details] screenshot showing how actions/icons can be put in the source message bar I'd actually meant the bottom-left "Synchronizing iPod" type notification. Using the black, bottom-middle "Disconnecting.." bar (what we call the Source Message Bar) would be fine, except, I want to be clear: we use that bar for source-specific messages, so switching to a different source (playlist, library, device, whatever) would hide it. Is that OK? Odds are pretty good you'll still be in the Miro Guide source when it pops up, so it's probably fine. We can also add buttons to that bar to switch to Podcasts, like how we in Podcasts show that bar to help w/ discovery of Miro Guide (see screenshot).
Created attachment 174052 [details] mockup using bottom left popup bar Here is how it could look if we would use the non-source specific bar that Gabriel suggested (sorry for the crappy layout of it, a bit tired after yet another conference this weekend). I would imagine this to slide up, stay there for, say 3 seconds and then slide down again.
Thinking about it more, I think I do prefer the Source Message Bar. As soon as you click 'Subscribe' we could pop it up w/ a spinner icon and "Subscribing to Foo..." message, and then change that to "Subscribed to Foo! [Switch to Podcasts]" or something. I think that would work well for this use-case. For a more general discussion of notification use-cases in Banshee, see bug #536253.
Sure, I think I'm leaning towards the source specific one as well, as you'll have some blinking feedback going on in the sidebar already and it's good if the action happens as close to the place where you did the action as possible. Can you make the bar disappear after a certain time period (not sure how long), so it won't sit around eating space until you close it?
Yes, that's not hard.
Banshee is not under active development anymore and had its last code changes more than three years ago. Its codebase has been archived. Closing this report as WONTFIX as part of Bugzilla Housekeeping to reflect reality. Please feel free to reopen this ticket (or rather transfer the project to GNOME Gitlab, as GNOME Bugzilla is being shut down) if anyone takes the responsibility for active development again. See https://gitlab.gnome.org/Infrastructure/Infrastructure/issues/264 for more info.