OK, this is one of those totally embarrassing moments, but I need to tell you that I have no clue whatsoever of chromecast.
I've done a little reading this morning and am still left with quite a lot of questions, maybe one of you can enlighten me.
chromecast delivers audio/video to speakers and TVs.
when applied to wikiloops and thinking of TVs, would that include seeing the screen and being able to navigate wikiloops from the TV, or is it just a convenient way to connect external speakers?
If there is no navigation option, then one would need to do the track selection on the mobile device and could enjoy the better sound of the TV, right?
What I didn't really get is wether one would be able to enabe Chromecast once (maybe based on the domain wikiloops.com), or wether one would need to start the cast on each and every track (which I'd find quite annoying).
From what I gahered from Nilton SO post link is that a quite chunky bit of extra code is needed to enable chromecast on a website, and to deliver that without asking the users to enable it first doesn't really seem a good idea to me - no need to slow down page load times todeliver features which are probably not instantly used by a lot of people.
Do you feel it would make sense to limit the option to playlists, albums and the radio?
Once we are talking about smart things, the thought to try to aquire the Alexa skill "play wikiloops radio" has crossed my mind lately, too... on the other hand, such fancy functions have the downside that people have the benefit of listening to our music without ever looking at wikiloops and generating at least some tiny advertising return that way. I'll have to see where wikiloops should jump that train, thanks for sharing your ideas!
Edited by
Dick on March 13 2018 09:53
Member
