Posted on 26th Oct, 2014 in Meta / Site Information
Hola! Cheers to another week in the books, it's Sunday and I'm three hours (and three espresso shots) into my work week. In the mean time, I'd like to introduce you to...
NEPTUNE (click it, silly.)
(please note -- Neptune is in active development. it's not even in beta. which means it probably won't work, a lot, for a period of time.)
Which is really just a cool way to say that I'm beyond tired of Soundcloud's consistant downtime, negligence in terms of resolution of system issues, and screwing me over time and time again when I try to sign up for SC Pro.
So, what exactly do I have planned for Neptune? Well, lets get started:
-
Neptune is an HTML5 cross-platform audio player. The demo already works on all devices I've tested.
-
Neptune is FAST. That's the point. I'm trying to use early implementations of the MCX CDN by utililizing coastal nodes, west coast go to California, East Coast go to Iowa or Chicago. With my 2-hits-per-day traffic, it's not a very useful test but it's part of the app!
-
Neptune needs to be pretty. The SC implementation of their services is ugly, bloated, and unusable. I want a combination of Spotify prettiness (which is still pretty bloated) with the SC infrastructure in terms of backend API availability.
-
Neptune needs to break ground -- I want to keep this project small and simple for now, I want it to become the implementation in which my music gets released, and we'll move from there!
- Native apps. I've got Neptune actually working (marginally..stupid Android device-type malfunctions) and some basic xCode/SWIFT done for the Neptune apps, however just visiting the demo in your browser actually works just as fine as well.
