For those interested, there is a Mac app called BeardedSpice that maps the media keys to a variety of websites (Youtube, SoundCloud, BandCamp, etc).
> Unacceptable Use
> use of the SoundCloud® API to aggregate and stream User Content from multiple users into an on demand listening service;
I've built similar things in the past (https://github.com/MeoMix/StreamusChromeExtension), but using SoundCloud's API for such a project always seemed off-limits from a TOS perspective.
Although, Soundnode doesn't seem to be a true native app, as others have pointed out.
The look & feel argument is total bullshit at least for me. Every native app I am using is completely different. The only consistent look & feel is with ms office apps like excel, word and powerpoint.
And yes, standards are still creating too high level APIs and it takes forever to gain more and more access to the same things native apps have. But that will get better due to extensible web manifesto.
Where the data resides is not a distinction between web apps and native apps. See Apple's bundled apps, like Notes, Contacts, etc.: you can access the same data via a website or through native iOS/OS X apps.
However, one advantage that native apps have when it comes to accessing cloud data, is that you can still access and update that data even when you have no connection to the internet.
> which is why Apple is deliberately keeping Safari in 2010
What do you mean with this?
> The only consistent look & feel is with ms office apps like excel, word and powerpoint.
This sounds like you are primarily a Windows user, where indeed, MS Office apps seem to be the only ones that share a consistent look-&-feel among them. Even Windows' own applets vary wildly in how they present basic UI elements (like toolbars and Control Panels.)
The overall situation, while with its own unique flaws, is much more coherent on OS X, across all vendors.
> Performance is also a lot about how and who wrote the app rather than if the app is native.
True, but web apps will always be removed from the underlying OS's "metal" by at least one degree, no?
Huh? The data is only accessible to native app after you have installed the app on a device. If you only ever use your own one desktop, then it's probably hard for you to see this. Can you even try to imagine that you cannot just install arbitrary native app on let's say, your friend's device to access your data? But you can easily "install" a web app, since technically it's just a website like this one.
> What do you mean with this?
> However, one advantage that native apps have when it comes to accessing cloud data, is that you can still access and update that data even when you have no connection to the internet.
> True, but web apps will always be removed from the underlying OS's "metal" by at least one degree, no?
Not always now that Web Assembly will be implemented by browsers. (Not to be confused with "asm.js", see https://en.wikipedia.org/wiki/WebAssembly)
Whether the UI of the standalone app is more polished that's debatable, but as far as "isolating a service to a program" and "being able to close the browser fully without closing down music" go - in and of themselves - using another browser in paralel looks sort of equivalent to it.
I don't rule out there could be some other advantages of this solution, like smaller memory footprint etc., I addressed the specific reasons given by the parent commenter
In general I'm a user who never downloads apps on my phone (unless there's something I find unsuited to my browser) - but for a music player I want it to be quickly isolated for skipping, pause, etc etc.
(Which I'm personally OK with for applications like this, where native gains may not be as big)
Thanks for that! :)
Although, this even makes it more difficult to understand this path.
you can obviously connect a usb cable to your computer to keep charging the phone.
- I use headphones, and I use Skype, so I wont use two pairs or swap them when Skyping. Skype for Desktop is easier to use than the phone (i.e. screen sharing, sharing links, etc).
- It is far easier to skip a track or pause it using a mouse when you're already using the mouse, than to take your hand away and use the phone.
- I can't watch YouTube movies on my PC when my headphones are in my phone.
People still get phone calls?
How exactly node.js makes it easy to do the wrong thing?
> While it's great to lower the bar to learning to program it also often results in great ideas that are poorly executed of which I think most of the nodejs community demonstrates.
What makes node.js lower the bar for programming? I personally find it not easier than C#. How is it different than, say, Python, in terms of difficulty? How is node.js community showing poorly executed ideas? Any examples or are you after FUD?
Stereotyping a community is the most unconstructive thing you can ever do to for this industry.
For me the less native apps the better
Also, the binaries are being offered for download over HTTP with no signatures.
Soundcloud's UI has gotten much better within the past year, enough so that it feels fine to use as a dedicated desktop app.
I then went to SoundCloud, logged in with the same account, opened up the list of the users I'm following, loaded until the end of the list, pressed Ctrl+F, typed in "fly", and no matches were found. I then went ahead and typed "spa", again, no matches were found. Then, I have started to be a bit suspicious about the app. Then, I started typing "Flying Spaghetti Monster" in the search bar on SoundCloud and immediately realized that I am indeed following a user named "Flying Spaghetti Monster", even though I absolutely don't see it through the list of the people I am following.
Talk about a bad user experience. I'm definitely not going to use their official website again.
Soundnode App UI looks nice. I'd add screenshot for each main view on app's home page, even if they're all similar, though. UX remains to be tested.
The only (apparent?) downside is that this app seems to be a bundled web app with web browser. I'm not that fond of such solutions. But. If it wasn't open source and GitHub page wasn't shown there, then there is a high chance I would not notice that it's built like that, at least from screenshot alone.
Writing SoundCloud client is on my ToDo list, as it would be a good way to brush up and enhance my Qt skills. Maybe I'd finally embrace QML along the way, as I'm postponing QML tinkering for far too long I guess. I'm also considering fiddling with PyQt5, as it could possibly quicken prototyping, but I'm not sure about it in my case, as I have only minor Python experience and no PyQt experience at all (well, it's like incentive to change that). There is also SoundCloud python package, so going python way is quite tempting, but I always prefer native compiled apps over scripted ones.
(Oh, it's already ~2 years since I first thought about writing my own SC API front-end. Time sure flies...)
But the login looks exactly like the official page. So is this just a wrapper for the website or do they actually add value ?
Used it for some time and is very nice.
I'm curious if the motivation of making a desktop app was just for the "installed app user experience" or because it was needed to access some API.
or does it scrap / manipulate the sound cloud client ?
is it allowed ?
Wonder what happened.