YOU DON'T HAVE TO LOOK far to find start-ups that sputtered and died when their core business processes depended upon access to Twitter's firehose or APIs. All Twitter had to do is change how a business could access its API and a complementary business would fold. Twitter's example has been followed by a number of other businesses, including Audioboom.
Screenshot from @Omaniblog on Audioboom.
In Audioboom's case, a decision to the company to introduce a log-in wall in front of anyone wanting to listen to a audio clip caused some upset. The Audioboom log-in wall meant many people could not simply click to hear recordings anymore. The log-in wall means you have to have a free account to listen to anything on the Audioboom system. Paul O'Mahony explains how that has affected his business. [MP3 File 5:38 stored in OneDrive]
The Audioboom embed player is a nice piece of code but I haven't embedded it on this blog post. Instead, I'm using Typepad's media play to share the MP3 file produced by the Audioboom app. If your browser cannot render HTML 5, you will see "your browser does not support the audio element" instead of an audio player above.
Audioboom's shuttering of easily-shared audio has led me to explore other social audio services in greater depth. There is a fledgling community in Voicebo but significant limitations exist there. Soundcloud already operates a formidable service but it does not permit uploading from a mobile handset. And the grandfather of them all is Libsyn, probably the service I will rejoin and use for the remainder of the decade.
[Bernie Goldbach teaches social audio as part of the creative multimedia degree programme in the Limerick School of Art & Design. The perspective shared in this blog post remain his alone. No institutional opinion is asserted or assumed.]