{"id":7911,"date":"2020-03-20T11:42:00","date_gmt":"2020-03-20T15:42:00","guid":{"rendered":"https:\/\/www.shortform.com\/blog\/?p=7911"},"modified":"2026-04-06T21:44:59","modified_gmt":"2026-04-07T01:44:59","slug":"dropbox-mvp-explainer-video","status":"publish","type":"post","link":"https:\/\/www.shortform.com\/blog\/dropbox-mvp-explainer-video\/","title":{"rendered":"The ORIGINAL Dropbox MVP Explainer Video"},"content":{"rendered":"\n

Dropbox is now a technology giant, valued at $10 billion in a 2014 funding round<\/a>. It’s a very complex product, honed over a decade of development and hundreds of millions of dollars of investment.<\/p>\n\n\n\n

But Dropbox didn’t start with the slick, seamless product you use today.<\/p>\n\n\n\n

So let’s go back to the beginning<\/strong>, before Dropbox had a polished product and thousands of employees. Back to Dropbox’s original Minimum Viable Product (MVP). If you’re an aspiring entrepreneur, be emboldened by the idea that Dropbox started with just about as much as you have right now<\/strong>.<\/p>\n\n\n\n\n\n\n\n

The Dropbox Explainer Video MVP<\/strong><\/h2>\n\n\n\n

If you haven’t heard of it yet, Dropbox syncs your files across all your devices. If you upload a Word doc to your Dropbox folder on your laptop, you can then access the same doc on your phone. If you then edit the doc on your phone, the saved changes will show up in your computer\u2019s version too.<\/p>\n\n\n\n

This is a very complex product<\/strong> to build, requires technical wizardry to integrate into the operating system, handle large files, deal with file conflicts, and more, all packed in a seamless user experience.<\/p>\n\n\n\n

Over a decade ago, when Drew Houston founded Dropbox in 2007, he knew the file sync problem was a problem he faced intimately, and suspected others faced as well. Famously, he forget to take his USB drive on a long bus ride, depriving of the files he needed to work. On this bus ride, he started building the first version of Dropbox.<\/p>\n\n\n\n

He had built an early prototype, but it was from seamless and bug-free. Drew knew his product prototype wasn\u2019t ready for a public launch yet, but he still wanted to gauge whether his product solved problems for other people.<\/strong><\/p>\n\n\n\n

So Drew recorded a video of his prototype, demonstrating its main features and use cases. He released his Dropbox explainer video MVP<\/a> to Hacker News on April 5, 2007<\/strong>, as part of his application to Y Combinator<\/a>.<\/p>\n\n\n\n

<\/figure>\n\n\n\n

At the bottom of the video was a form to join the waiting list for the private beta.<\/p>\n\n\n\n

Why was this a Minimum Viable Product? In the Lean Startup framework, this video \u2018product\u2019 tested the value hypothesis<\/a><\/strong> \u2013 that people actually faced a file sync problem, and Dropbox was the solution to that problem.<\/p>\n\n\n\n

This Dropbox MVP was simple and not ready for public use. It worked only on Windows, and Drew Houston hadn’t developed a Mac port yet. It probably couldn’t support more than dozens of users at once. But if you use Dropbox today, you can see the core principles of how Dropbox works in this early Dropbox MVP<\/strong> – it got the point across. Potential users didn’t even need to use the actual product<\/strong> – the video explainer was compelling enough to answer the value hypothesis.<\/p>\n\n\n\n

The video hit a nerve \u2013 because it so clearly showed the benefits of the software, it drew hundreds of thousands of views. One commenter says:<\/p>\n\n\n\n

\n

This is genius. It’s is problem everyone is having, and everyone knew it. If it really works as well as it looks in that demo then they nailed it.<\/p>\n\n\n\n

-brett<\/p>\n<\/blockquote>\n\n\n\n

The Dropbox explainer video MVP showed why the Dropbox experience was magical, how you could instantaneously make a change on one computer and see it reflected live online. They grew their beta waiting list from 5,000 to 75,000 overnight.<\/p>\n\n\n\n

Clearly, after this point Dropbox still needed to deliver with an actual product (which they did). But Drew was now confident he had tapped into a problem lots of people felt but no one was solving.<\/p>\n\n\n\n

In fact, Drew didn’t even need <\/em>to have coded up a working version of the product<\/strong>. If he wanted to simplify the Dropbox MVP further, he could have just mocked up the product’s behavior, showing file changes with sleight of hand and editing. (If you do this, though, you need to be sure that you have a remote chance of being able to build the technical solution. Read about Concierge MVPs<\/a>).<\/p>\n\n\n\n

Iterating on the MVP<\/h2>\n\n\n\n

When something works, iterate on it to get even more mileage.<\/p>\n\n\n\n

In 2008, a year after the original first Dropbox MVP above, Drew Houston made another explainer video, this time with a Mac client, and many more jokes. It’s much more polished and shows greater capabilities than the first Dropbox explainer video:<\/p>\n\n\n\n

<\/figure>\n\n\n\n

This video got even more press, leading to mentions in tech news outlets<\/a> and thousands of people joining the waiting list.<\/p>\n\n\n\n

Dealing with Critical Feedback<\/h2>\n\n\n\n

As usual, not everyone was a supporter.<\/strong> And if you launch your own Minimum Viable Product, you’ll likely get mixed feedback too. (Some people love being critical.)<\/p>\n\n\n\n

Some said the Dropbox explainer video didn’t show a full replacement for USB drives, as was promised:<\/p>\n\n\n\n

\n

The only problem is that you have to install something. See, it’s not the same as USB drive. Most corporate laptops are locked and you can’t install anything on them. That’s gonna be the problem. Also, another point where your USB comparison fails is that USB works in places where you don’t have internet access. -nickb<\/p>\n<\/blockquote>\n\n\n\n

Others said Dropbox was unnecessary for someone with enough technical experience<\/strong>:<\/p>\n\n\n\n

\n

For a Linux user, you can already build such a system yourself quite trivially by getting an FTP account, mounting it locally with curlftpfs, and then using SVN or CVS on the mounted filesystem. From Windows or Mac, this FTP account could be accessed through built-in software. -BrandonM<\/p>\n<\/blockquote>\n\n\n\n

Finally, others questioned the business model<\/strong>, based on storage costs:<\/p>\n\n\n\n

\n

$0.15 per GB-Month of storage used. <\/em>$0.20 per GB of data transferred.<\/p>\n\n\n\n

So, that means Dropbox is going to have to resell S3 at a premium for the added value of these nice Coda-like features. Would you pay a premium for these Dropbox features? Maybe, I don’t know.<\/p>\n\n\n\n

Also, what’s the typical use case? How much bandwidth\/storage are people going to consume? Because, if I store 100 megabytes… my bill will pennies every month (going on S3 prices). You cannot transact pennies per user per month. If you could, then you’ve cracked the micropayments problem wide open. Maybe there would be a base fee? Like $5\/month or something. Would people pay that much for online storage? -jganetsk<\/p>\n<\/blockquote>\n\n\n\n

Now, Dropbox is now a worldwide company worth billions. So clearly it got many things right along the way.<\/p>\n\n\n\n

But that doesn’t mean the commenters were wrong.<\/strong> These were legitimate concerns. Highly technical people were<\/em> indeed building their own solutions. And it was <\/em>unclear whether anyone would be willing to pay for a convenience layer on top of commoditized mass storage.<\/p>\n\n\n\n

But you don’t need to please everyone. And you shouldn’t even try. As Paul Graham suggests<\/a>, “Sometimes the right unscalable trick is to focus on a deliberately narrow market. It’s like keeping a fire contained at first to get it really hot before adding more logs.”<\/p>\n\n\n\n

Drew Houston was convinced that there were plenty of people who:<\/strong><\/p>\n\n\n\n