The concept of a livestream isn't new at all, but there are a thousand subtle things that are slightly different (http://austenallred.com/_site/the-subtle-things/). The way they're tied into Twitter and riding an already-existing social graph, the widespread adoption of mobile, the availability of bandwidth and the acceptance of ephemerality are all completely different than Justin.tv or the many other attempts in this space.
Interesting. Makes me wonder if there's value in shipping multiple pivots of the same concept when keeping multiple paradigms in a single app could be confusing. Sort of like a/b testing at the app store level, or purposefully unbundling yourself.
+1 for the buzzword-density of your post, but I also find that to be an insightful idea -- only problem is that many times one is blind to the alternate 'pivots' that you might was to ship versions of.
Plus, the development of any given 'pivot' is not necessarily trivial, and could be beyond the skills/resources of a company/person to do so.
I would say the new thing about Meerkat/Periscope vs Justin.tv is that Justin.tv seemed to be marketed as kind of a lifestyle (that appealed mostly to assholes), where as Periscope or Meerkat seems like something you can do on a lark, more ephemeral, not something that defines you.
I think there is an interesting conversation to be had about why, in a world with LiveStream, UStream, & YouTube Live Events, people see Meerkat/Periscope as revolutionary. Also apply that question to Spotify vs Rhapsody.
Timing. I was a Rhapsody user in 2003. I even had an AV receiver that supported Rhapsody back in 2005 or so, assuming it was connected to my computer (for stuff like track listing and whatnot on the device). But it didn't take off because timing wasn't right. People were just at a place to start buying digital tunes -- streaming music was awkward.
But beyond that, it took the iPhone (and devices like it -- but really, let's admit it was the iPhone. I loved my Treo, BlackBerry and Windows Mobile devices too, but it was the damn iPhone) to usher in a device where people could stream on the go. Before that, using Rhapsody (or even Spotify, early on) was kind of a PITA.
Spotify made it easier by letting you sync offline stuff with your iPod or iPhone, but it took widespread 3G and beyond, good data plans and saturation of smartphones for people to be like, "yeah, I can replace my iTunes with streaming music."
The same is, to me, true of streaming video. You could do live streaming close to a decade ago. On your cellphone. Shit, I remember envying people using Qik on the Nokia phones in 2008. But it took a long time, there was massive latency and the quality sucked.
Meerkat and Periscope are fast, easy to use, have restreaming features and are easy to drop-in, drop-out of.
Whether they last or not, I don't know. But just as it took e-sports to make the Justin.tv model work (and I remember when they launched Twitch. All of us, myself included, thought it wouldn't work. But then the devices for livestreaming game videos became so inexpensive and the experience so compelling, Sony and Microsoft built it into consoles. It took the barrier getting super easy and the content being compelling for the user case to be seen).
Pretty much. I was a Rhapsody users, too, and I loved it. It was, like, 90% of magic. But Spotify is 100% of magic. And it's that last 10% of magic that matters. With Rhapsody, there were a lot of things that broke the illusion and made you think about the underlying model of how to download songs, how to get them on your device, how to renew your licenses. Spotify doesn't make you think about anything, it just lets you listen to music, as much as you want to, and a pretty clever facsimile of whatever you want to.
Speaking of timing, we can even say the same thing about Twitch.
Video game live broadcasting existed as early as 2005 from Korea, where we would get a 240p stream from OGN (a Korean cable channel), which would sometimes get replicated over users' personal servers. Only the most hardcore Starcraft Broodwar fans stayed up until 3am to watch these games live though.
Again, I would say good timing. They tapped in on teh fact that people like watching gameplay videos and they built a great system that made it easy for people to use what were becoming affordable video capture frontends to publish live streams.
And its a niche, but it's in a sense, a way more accessible niche than watching a random person lifecast. You're watching someone game. Which isn't that different from watching people play sports on TV.
With hosts in 34k cities (from article), airbnb probably has more employees if we classified hosts as such. Also, many hosts hire of cleaners. It's quite possible that ~500k people are earning income (directly or indirectly) related to airbnb bookings.
Question: why didn't any of these issues prevent the web from taking over the desktop during the years between 1995-2005? Native has always been faster and more feature rich, on every platform and at every point in time.
Really? If you use Windows, you should be familiar with Windows Explorer. Since Win95 with Internet Explorer 4 desktop refresh (shipped also with Win98) you have a trident (IE) web engine in Explorer. The side bar with the metadata and info is DHTML in Win95(IE4), 98, ME, 2000. And a fork of trident code is used in XP and newer. Also WinXP "Software" application to uninstall programs is basically DHTML based. The newer control panel pages, the newer dialogs, etc. The EU demanded that Microsoft has to document the new UI-engine, used in IE "addons" dialog, Vista/7/8/10 Explorer bars & shell dialogs and Office 2007+, so that there no completive advantage. One has yet to find that in MSDN.
1) Microsoft made Windows too damn fragile. Installing the app means that setup.exe will write all over the hard drive, and uninstall was never easy. Web didn't required install/uninstall.
2) Windows programs, with a few notable exceptions, were/are butt ugly. Web started as an ugly abomination, but designers catched up quickly. Web applications, even then, on slow connections, often provided more pleasant experience.
Web app on mobile today doesn't have the same luxury - native app install/uninstall is painless; native applications are better integrated and most of the time handle unstable connections better; good native apps are beautiful and often have superior usability compared to web apps.
I think its because the bar for native apps wasn't that high back then. Also the interactions required for desktop apps are much simpler than mobile apps, where gestures are key part of interactions. Gesture-based animations is actually part of using the app, instead of on desktop where they just make things look pretty.
Most desktops are far overpowered for the (relatively) trivial computing tasks they are used for. As a result the relatively poorer performance of the webapps most people use desktops for is masked to a large degree, where it's even relevant.
In the context of this article, a big portion of the risks and costs are supported by national health care (Obamacare). If these gig workers had to acquire health care via the old means (i.e. benefits from a corporation, or hoping an insurance co will accept you), they would not have the luxury to work as contractors.
ACA/Obamacare is not national health care - it's national health insurance, and despite it being better than before (i.e., no pre-existing condition rescissions), the plans offered by carriers even with subsidies are still too pricey for many.
The mistakes you listed make it sound like you're trying to move too fast. Moving fast is good when it comes to product development. But not on the business side. Just focus on these two things:
1) Find a few users who love the product
2) Improve it to the point where they start telling people about it
Forget about analytics, pricing pages, press, etc etc. If you can't get some family and friends to rave about it, you won't get the masses.
Realistically, it will probably take years to really nail 1) and 2) above. But once it happens, you'll very quickly become the next big thing. Read up on the history of Pinterest for a great example of this.