Music Venture Capitalists

While reading a recent Wired article by David Byrne on the brave new world of music and an artists new set of options for distributing and promoting their work, a quote from Brian Eno struck me.

“The only idea they have is that they can give you a big advance – which is still attractive to a lot of young bands just starting out.  But that’s all they represent now: capital.”

- Brian Eno on record labels.

It’s a simple observation, but it felt incredibly perceptive and it got me thinking.  For some time now, everyone has been talking about how the traditional music industry is totally changing.  These discussions frequently include the predicted demise of the traditional music label. 

So, if a label was really truly willing to completely rethink their business model, what might it look like?  If the biggest thing they can add to the equation of growing a successful artist these days is capital, then why not focus on that?  It’s your core competency. 

Acknowledge that all the rest, much of which – I’ve read, I have no direct experience – is now subcontracted out, of the services a label provides are either seeing their costs go to zero (recording, distribution) or can be dealt with by the artist creating their own direct business relationship (marketing, promotion). 

For those labels that feel they have solid in house offerings in these areas, spin them off.  Make them stand alone businesses that will succeed/fail on their own.  For the core label that’s left, now it’s just an investor in new artists.  Said another way, the music labels become venture capitalists in the same way that they behave in the technology industry.

The relationship would be the exact same.  Some tech companies get started by the founder’s life savings and credit cards.  However, many still get funded “the old fashioned way” – venture funding.  These folks want to have some semblance of pay while they’re building their product, and need to hire outsiders (engineers, PR agencies, marketing, whatever) to drive it to success.  For these folks, up front funding is needed.

For music, some artists will scrape by on their own and do it all themselves and some will want up front cash to allow them to get new gear and eat while they create their music.  The later will “pitch” their early work and creative vision, and the venture firm will decide if they want to provide them funds in exchange for partial ownership.

Like traditional VC’s, music VC’s can and would provide advice and have suggestions for vendors in music PR, or how to do a ringtone deal.  However, that wouldn’t be something that they directly do.  Again, they act as advisor (as they want to see their investments succeed) and they act as a “friend” that has connections in the industry when an artist needs them, but they no longer have all the in-house noise.  The resulting company would be a lean and mean organization consisting of 10′s of employees, not 1000′s.  They would take their investors money, and they would place bets on what music was going to do well. 

Unfortunately, I doubt the traditional labels will really do such a thing, I am more a believer that they’ll continue to trend to extinction.  However, that may mean that there might be an opportunity for someone else.  Someone who has cash  and who’s used to such a working relationship.  Perhaps our Silicon Valley VC’s – with the cash they cannot figure out how to invest all of – might diversify further.  What the heck, it doesn’t feel any crazier than seeing them fund new car companies.

Blackberry Fanboy-dom & Crummy Pumatech Sync

My friend Omar is fond of pointing out the inconsistencies of Mac Fanboy arguments.  Their predilection for broadcasting in favor of their beloved OS/machine platform; how they’re prone to highlighting the great things that Apple does; how they tend to gloss over or (better yet) provide apologies for the things that Apple falls short on.

I fear that I may have become the equivalent for the Blackberry (and I fear that Omar may have the same opinion <grin>).  I certainly have become a strong “net promoter” (marketing lingo for someone who uses your product/service and would recommend it to a friend).  In the six months since I’ve returned to owning a Blackberry, I’ve also gotten my wife to buy one and more than a few friends to strongly consider it. 

Also, just the past weekend I also convinced my father to pick one up.  After years (and I do mean years, and generations) of Windows Mobile phones that barely worked, he had come to expect that the price for smartphone functionality and flexibility was poor reliability and complicated UI’s.  After his first couple days of Blackberry use, I asked him how it was going (for the record he picked up the new BB 8830 from AT&T).

New phone is fantastic.  Still learning but works so much better than anything I  have ever had in so many ways. 

Now, my father is the first person to complain loudly when technology doesn’t do what he expects and wants.  This does not mean that he won’t use it, he’s an extremely early adopter (often to his detriment, let’s just say the Vista upgrade was not seamless).   So, what I’m saying is, he uses technology frequently, and this is rare praise from him.

All’s Not Perfect

I, of course, still love my 8800.  However, in the interest of not glossing over shortcomings (perhaps avoiding total fanboy-dom) there is a piece of the puzzle that continues to frustrate.  Simply, the tethered sync program (to sync between your PC and the device when you don’t have a BES in the equation) is a miserable piece of junk.

It’s a poor product that provides few configurations or options.  However, that’s not the really evil problem.  The really evil problem, for me, is that it doesn’t work.  Almost since I started using it, I’ve had an on-again/off-again problem with the sync just bombing out and ending with the PC application crashing.

The specific problem seems to be some types of calendar events in my Outlook can get into a state that the sync engine just doesn’t play nicely with.  If I avoid syncing the calendar events, all is well.  Further, if I just wait the sync window of the calendar will pass over the offending events and will start syncing correctly again (for awhile anyway).  Finally, if I reset the sync relationship, it usually will let the initial post-reset sync work, but subsequent may or may not.

So, what does all this mean?  Well, as a technology guy, I’m still trying to piece together and debug what is happening (and if I figure it out, will no doubt post on it).  However, as an end user, it means that BB sync for non-corporate types kinda sucks.

Unfortunately, I’m not terribly surprised.  I’ve been around devices and sync protocols/technologies as a job for going on 7 years now.  Blackberry’s desktop sync conduit technology is not their own.  Instead, it’s licensed by a shop called Pumatech.  And as folks “in the know” know: Pumatech sucks.

Of course, there is no Pumatech technology in Blackberry’s bread and butter products (sync between their devices and Exchange).  No no, that’s all built in house by RIM.  The outsourcing of the desktop solution comes as a result of non-corporate users not being the original sweet spot for RIM products. 

Such non-BES customers have always been second class citizens for RIM.  However, the reality is that if RIM wants to continue to see growing market share (and a growing stock price) then their users cannot be assumed to be mostly corporate. 

RIM clearly does recognize this at some level.  It is being reflected in their new device designs (they look much cooler – no longer the boxy volvo of smartphones – and they now have consumer focused features like cameras and media playback) and their marketing.  However, it seems clear to me that they have not yet dealt with this at a software level.  If RIM truly cares about this market, they are going to have to bring their desktop software solution totally in house.

Lack of Will or Lack of Ability?

I worry that RIM doesn’t “get it” on this front.  In a past life/startup, I used meet and work with many folks at RIM.  The tenor of the place all those years ago was that they were amazing gizmo makers, top flight telecom protocol guys, and competent enterprise server makers.   What they absolutely were not were user-focused desktop software guys. 

In the “actions speak louder than words” department, RIM seems to still be this type of engineering shop.  They have made no efforts to pressure improvements on Pumatech (or to bring desktop sync in house).  Further, their new picture, video, audio solutions are similarly worrying.  The features are very consumer oriented, but the choice of licensing and outsourcing this desktop sync UI and product set to Roxio smacks a bit of “here we go again”.

I would love to see RIM grab ownership of this stuff and apply the same discipline and precision they have to device creation.  If they want to play in the world of iPhones, with a full integrated end-to-end user focused software stack, they’re going to have to.

Better Privacy Screens

As I mention all too often, I’m on planes a lot.  I also compute a ton when I’m on the plane.  My weekly transcontinental commutes are 4 hour uninterrupted compute sessions.

So, I’m keenly aware that as a good travel citizen I should keep my own eyes on my own screen (or if I’m not computing, my own book/magazine/seat in front of me).  However, I cannot help myself, I often find myself sneaking peaks at my fellow traveler’s screens.  When walking the aisle to the bathroom I find myself noting how many folks are watching movies vs. working on Powerpoint vs. practicing poker.

My nosiness may be rude and poor frequent flyer etiquette, but it isn’t nefarious.  However, I have heard of firms that make a living by flying folks about the country and having them spy on computer users looking for corporate secrets.  This is a problem.

The unintentional sharing of sensitive corporate information on flights is something that many a corporate leader has fretted about.  I have one family friend who, when an exec, strongly discouraged his team members from using their laptops on the plane at all.  He’d rather loose that productivity time than risk the lose of sensitive deal negotiation data.  I’d even venture that this issue only gets worse and worse as the airlines continue to shrink the distance between their passengers. 

All this worry has led to the creation (at least in part) and use of laptop privacy screens.  I have tried using one of these myself.  However, I eventually abandoned it for the following reasons:

  • Has to have a film/plastic shield over the main screen, which allows “gook” to collect between the real screen and the protector.
  • Darkens the screen.
  • Hassle not needed in the 90% period (e.g. when at work or when at home).

I was dwelling on the dissatisfaction I have with privacy screens (and many others must too, because almost no one uses them on flights that I fly – even the ones that are at least 80% business travelers), when I found myself wondering if a better solution couldn’t be found.

I wondered if it wouldn’t be possible to devise a method that makes use of “3-D glasses” style stuff + software (blur mode on the screen + glasses = clear image).  Of course, glasses wearers would be problem (and you may need to have something work so that there were frequencies tuned certain glasses – lest your neighbor have the same glasses). 

I suspect there will continue to be little innovation in this space until corporate IT folks (and it really can’t be far away can it – they worry about data loss constantly these days) begin mandating privacy screens left and right.  Once they do, and once they realize that no one is using these screens – removing them from their machines as soon as they get them – there will be a demand in the industry to have “policy enforcement”.  The same type of thinking that has create situations where you have to use a PIN to access your mobile phone that has corporate email, will demand a new solution to this problem.

Java: A Looser in my Browser

I was checking out a new startup noticed in the never ending stream of same reported by TechCrunch.  Its name is Fuser, I was intrigued.  I headed over to the site and blamo, ran into the reason I would never return.  Java.

I was a Java programmer for ages (or at least what passes for “ages” in the computer business).  I started out coding in pre-Java 1.0 and my god was it a rocky road.  As the platform matured, it became clear what it was good at and what it wasn’t.

It was, and is, a reasonable choice for server side coding (especially when multi- platform support is a concern).  Where it isn’t a success is the client side.  Browser applets were miserable to develop, rarely worked, and required client side code (the JVM) that wasn’t available by default in all platforms – I’m looking at you Windows – and was non-trivial for users to install.  In the late 90′s (and even early 2000′s) Java was really still only viable client choice for many in-browser UI scenarios, but it was avoided by most developers I knew at all costs.

I remember working very hard to make rudimentary DHTML (that’s a precursor to your AJAX, for you hip kids of today) behaviors work.  All to avoid needing a heavy handed UI in Java.  Now, the technology palette available to the web UI developer is amazingly rich: AJAX, Flash/Apollo, Silverlight are just the front runners in a very busy space.

With this new options available to any web developer that bothers to learn one of these newer (they’re really not even “new” anymore) technologies, the interaction options inside the browser are almost limitless.  So, in this new age, why oh why do people bother to still use Java Applets?

For the most part, they’ve become a rare oddity.  I almost never come across one unless you’re on some backwater real estate site (this industry seems to have been sold a bill of goods by some vendor for showing 360 picture views and walk through’s in an Applet), or some crusty old web application that is hasn’t been updated in a decade.

As such, after my more recent Windows rebuilds (and certainly now that some of my boxes are on Vista) there is no longer a JVM on my personal machines.  If you bother to use Java on your site, I – more often than not – will just depart it as soon as I realize your technology requirement, never to return again.

The Java Applet era is over, any web developer that doesn’t get that is in trouble.

This News is Rotten, Please Throw it Out

As I’ve blogged about before, I have fallen in love with Google Reader.  It has just the right amount of flexibility for my news reading needs.  Where others had failed me (including the very powerful, but still constraining – for me - FeedDemon) Google Reader seems to have succeeded.  Of course that doesn’t mean that there isn’t plenty of room for improvement.

In one such area, I cannot believe that I’m the only user out there that has problems.  I basically have two types of feeds that I subscribe to, one type are infrequent posted or very high value feeds, where I want to read (or at least see and decide not to read) each post that comes from the feed.  The other type are true “news” feeds.  These may be “real” news like the New York Times and TechCrunch, or idle chatter feeds like Valleywag.  Nonetheless, this 2nd type of feed is not well serviced today.

These feeds generate a huge amount of daily traffic.  On the days where I can keep up with it (I do have a day job) I’m not sure I want to.  However, if I actually step away from using Reader for a day or two, the backlog on these feeds can be crushing.  What I want to see for such feeds is the concept of decay.

Said another way, feeds that are highly time sensitive should have the option of aging out in my reader.  I don’t like seeing that Techcrunch has 251 unread items (it stresses me out, this same stress is why I cannot use feed readers that overload the concept of email – more inboxes to triage is the last thing I want).  In reality, I only really care about the last 24 to 36 hours of posts from such a site.  Any older unread posts should age out of my unread information.

Of course, as I note, I don’t want this behavior for all feeds I own.  Instead, the decay of posts should be a per-feed setting (or maybe/also per-folder, if you’re an “organize feeds into folders” type of person). 

Extra points if metadata could be saved to note if something was unread, read, or unread and aged out for later historical search filtering.