But their WhatsApp business model was not self sufficient. They were charging $1/year which is less than the operating cost of the servers and bandwidth.
> They were charging $1/year which is less than the operating cost of the servers and bandwidth
Are you sure of this? If they have a billion users, they're earning a billion dollars a year off of this. Considering that they don't need to store messages for an extended period of time, or run analytics, do they really need all that much?
Most people weren't actually paying. Apparently, the vast majority of users were granted free lifetime memberships (see comments here [1] and article here [2]). When Facebook acquired it, it only had $10 million in annual revenue [3] against 450 million users. Clearly, most users were jumping on board during times when it was made available for free.
Do you need more than $10M/year for 450M users? As I've said in another comment they barely stored anything server-side and it's known they have a very optimised stack
You do if you’ve been acquired for $19 billion. The founders couldn’t have been naive enough to think that Facebook and its shareholders didn’t have a need to monetize such an enormous investment. Facebook is not a charity, it’s a business.
Facebook monetizes Whatsapp by limiting its growth. You can easily think of all the “social” functionality Whatsapp could have added in competition with FB and Messenger.
That is what I am seeing now here in India, folks in my circle barely post anything to facebook now, all pictures, status messages are on WhatsApp now.
If you didn't bother reading and contemplating, here's the gist:
There is no wolf to fear. We are all finite beings with finite time and resources. You 'stealing' his hypothetical business model doesn't really accomplish anything except tie up your resources retracing his steps. You would be the fool reimplementing the pipe.
Now if you are the type of person who reduces life down to only pursuing the almighty dollar rather than trying to solve difficult extant problems... Well... Maybe that would be worth it to you. Even then though, he has already captured his audience, and he'll likely have a reputation advantage over your copy.
Is this new? I tried it out a couple years back on a decent spec phone and it was the slowest app I've ever used. I'm pretty sure Snapchat the app was known for being sort of a wreck at some point. My daughter still put up with it but it was painful to watch her use it.
I have a fairly high end Android phone (OnePlus 3) and Snapchat freezes up all the time. Video pretty much always stutters without fail. IIRC it was the same on my Nexus 5 as well.
Not to mention the video someone posted beloew from an engineer talking about Erlang there in 2014 has some interesting numbers. Christmas/New years is peak, and on Christmas Eve they were maxing out at 146GB/s out.
If we assume they maybe averages 75% of that over 6 hours, that's 146Gb/s * (60606)s / 8bytes/byte * 0.75 * 0.05dolars/GB = $14,782.50 for a 6 hour period (estimate).
That's highest listed bandwidth tier price for Azure, I'm sure they would pay less for a number of reasons. But let's just say that $10k for a whole day may not be out of the realm of possibility. That puts bandwidth costs possibly North of $3 million a year. Even at $1 million, that's a lot of money.
Ok but a serious company wouldn't pay per byte if they were trying to save money. They could buy that much connectivity for like 50k a month. (Though they'd need to get some switches and have a network engineer.)
And if that's audio/video Vs just text, clever NAT hole punching techniques could reduce it if truly needed.
But, it seems WhatsApp was on SoftLayer? In that case their costs might have been vastly higher.
I find that hard to swallow for a small company size, such as being discussed here. Do you have a reference or some reasoning to support this? I'm interested to know where it comes from.
Benefits, office space, equipment, T&E, employment taxes, etc. This is an old article but it suggests about 2.7x. [1] I agree that it might be less for a startup assuming a frugal startup but it's probably at least 2x salary on average.
I'm not sure a ratio-to-salary is the best tool here. I mean, why would a developer on $150,000 have twice the healthcare cost, or office space cost, or equipment cost of one on $75,000?
I started paying before they were bought, I might even have paid twice and I loved it. Would happily paid for a few famuly members as well.
Also there should be a huge possibility to increase revenue by selling API access (think appointment reminders etc as well as the whole bot ecosystem).
When Telegram started they talked about price and I think I remember being unconvinced. I wanted to pay. As we (used to) say here on HN: if you're not paying you are the product.
(Of course now we have learned that some companies charge us and still sell our (meta)data and advertise to us.)
In 2015, when WhatsApp had ~1B active users, Facebook said that the overall revenue from it was insignificant enough they they were just making it free. I'm pretty sure it wasn't charging the vast majority of users (which is how it got popular in developing countries in the first place).
> Facebook said that the overall revenue from it was insignificant enough they they were just making it free
Have you considered that Facebook might not be telling the whole truth?
"insignificant" compared to what, how much money Facebook makes off of every extra user (who wouldn't want to pay) on their platform? Making it free can only be a profitable move because of what Facebook could do with the data, not because a few million dollars a year is truly "insignificant".
Articles I read when Facebook bought them said they were losing money. Most reports I just Googled were subscription only or plastered with ads but here's financial sheets:
WhatsApp began as a "status" service. Original iPhone had no background or push notification; user had to start the app to check others' status. When Apple added push notifications to iPhone, they added this to WhatsApp allowing status to be "broadcast".
Users in Europe were paying high prices for international SMS. These users saw that broadcast status notications were similar to international SMS, but free. Some of them suggested this to WhatsApp and so WhatApp added messaging.
Then the app took off.
WhatsApp used FreeBSD, Erlang and SSDs when, according to Koum, everyone in Silicon Valley was using Linux, Apache, MySQL, Perl (LAMP) and HDDs. Compared to others in Silicon Valley, WhatsApp had far fewer servers and employees per user.
at the time of accusation, WhatsApp was running on 16 servers! Erlang is idle for communication, they had like 1 million concurrent user on each server!!!
It feels like modern web design practices have grossly skewed people’s estimates of what it costs to deliver a service. Text messages are not fundamentally hardware intensive to deliver - unless you add tracking, “machine learning”, ad delivery, and mountains of JS for serving the app itself dynamically.
Twitter's failwhale-heavy Ruby experience is a good example. Ruby and especially Rails are good examples of trading hardware for programmer convenience. This is absolutely great when you're banging out an in-house app for 100 people, and there's no problem spending $1 per user-month on hardware. But Twitter's revenue is only $0.60 per user-month, and they need to spend on things besides severs. There is a reason that they needed to switch away from Ruby to a much more complicated architecture: https://blog.twitter.com/engineering/en_us/topics/infrastruc...
I also saw some people go the other direction. They had a Java app for serving a high-volume website. But the developers had a rewrite itch, and the execs were afraid they couldn't get acquired without a more hip technology stack. They even hired a fancy consulting firm to help, but when the first version was ready to go it was incredibly slow. Like two orders of magnitude slower to render a page. The rendering times were considered normal in Rails-land, but were a real problem at volume. So they spent another 6 weeks putting in a lot of caching while the ops people ordered a bunch more hardware.
We use erlang for managing our device messaging, I've seen the board in the office crawl up to simply obscene numbers of connected devices... on one server. Multi millions.
To be fair it's tiny little messages, I'm talking one device does maybe a meg a day after communicating constantly
There's a talk one of the engineers gives[1] (that someone else posted here so I'm watching it) about their architecture that's published in March of 2014, and in it he talks about ~550 servers, which includes 250 multimedia servers and 150 chat servers.
The only places he mentions 16 is when he talks about the "multimedia database". I think there were 16 sharded database servers.
I agree that what they did with server utilization was impressive. However the blast radius was pretty huge if something went down. Also wouldn’t scale to images/video very well.
Why can't it? End-to-end encryption means you don't need to hold on to pictures for lengthy periods of time, and video calling can be done without a centralized service.
Neither of those costs anything extra to run though. Since it's end to end encrypted with no sever backups the images and video can be communicated directly between the clients, WhatsApp just plays matchmaker.
It could, but that's not how it does, they store the (encrypted) media in their servers so that both phones don't need to be online at the same time, and also to avoid having to upload multiple times when you send to a group.
That said, they shouldn't need to keep them around for that long, unlike FB and similar.
Even at $1/year - their 1.5 billion active users should be an equal amount of revenue. I'd say that's enough to cover the cost of servers and bandwidth.
But that is it. If all you want is basic messaging then you are probably right.
However, if you are trying to build a messaging platform, which is what probably FB intends to do, then it requires more investment. Today, you might think that that is where the problem. All the users really want is basic messaging. However, in 3-5yrs from today, the reality may be very different (see WeChat or LINE in APAC) and WhatsApp maybe a complete misfit in that world.
All good products evolve. For something like messaging, if all you provide is a basic product, then you risk yourself being taken over by default platform apps (such as what happened with iMessage on iOS in US). You need stronger lockins and FB is well suited to provide those.
