What do you usually prefer when you use applications storing your data?<p>- Keeping your data locally?<p>In this scenario you have everything on your machine. You can easily backup it. Access from different machine won't give you data that you stored on other machine, unless syncing between them is implemented.<p>- Keeping your data remotely?<p>Biggest advantage is that you can conveniently access data from any machine (connected to internet). Biggest drawback is lack of full control over data. If server (or cloud, if you insist) is down, there is nothing you can do, unless local full off-line caching is implemented.<p>I prefer keeping stuff locally. If you use desktop and mobile apps for instance, then syncing apps on LAN, without need for additional server, is nice and very efficient, even if a bit less convenient.<p>---<p>Context (only for curious):<p>I want to create standalone desktop (maybe Android later too) SoundCloud client that will solve most of my problems regarding bad UX in their current web UI. SC API doesn't provide all the functions you have on site (at least officially), so such client may not provide exactly the same functionality, but I still believe I'll be able to deliver (if time will allow that) something that will bring actual UX improvement, especially to devoted-listener-and-commentator workflow. Discovery and uploading features will be post-poned for later.<p>What would be stored by this client? All user's data from SC, i.e. tracks, playlists, comments, so it would be kind of SC user account backup, but there would be also additional stuff too, like number of your plays of others' tracks. By keeping all your SC user's data outside of SC, you'll never lose any trace of your comment that track owner deleted or deleted the track it was left on.<p>Hopefully in upcoming weeks I'll post on HN link to email + SC login signup page for those interested in being informed about availability of first alphas.