The app has over 10 million installs on Android alone.
Alphabet has 117 BILLION DOLLARS cash on hand.
Why is it worth screwing over how ever few people were using this?
Let's say a team to maintain an app like this cost 2 million dollars a year.
For 1 ten thousandth of their cash of hand, they could fund this app for 5 times longer than Homo sapiens have walked on earth. 1.1 million years.
Even if Google shuttering apps is just a meme, why is it even worth feeding the meme when you have such mind bending amounts of money and revenue?
-
Of course the answer people will reply with is "they have better things to do with the resources".
That's the mentality that makes people not trust Google.
When you have such mind bending amounts of money, something can be successful by the standards of mere mortals and an embarrassment to Alphabet. No one wants to rely on a company that sees your money as a joke and will gladly pull the rug under you.
This app is a perfect example, what kind valuation do you think an app with 10 million installs for neighborhood engagement would see? We don't have DAUs, but you could literally value a listing with 10 million users in the millions.
The problem with this reasoning is that the numbers will start to look a lot less practical if we consider the total number of projects Google has shut down. If we applied this reasoning each time, they'll be out of cash a lot sooner than your estimate.
I'm all for abandoning projects that makes no sense to maintain. But if this happens too often, then somewhere along the decision chain people are missing the mark on what's worth building and supporting. In Google's case, they should probably put a bit more thought into it before releasing something to the public. This situation, to me, is a sign of overconfidence among Google workers about their abilities. In humbler places, they do side projects too but before they start them there's a lot of discussion about the purpose of the project beyond the code and the value it brings. When I saw the list of projects Google had killed, most of those projects looked plain boring to work on and seemed like undergraduate projects. Then again, may be it's it's own strategy to build as many stuff as you can quickly hoping some of them might take off.
> But if this happens too often, then somewhere along the decision chain people are missing the mark on what's worth building and supporting. In Google's case, they should probably put a bit more thought into it before releasing something to the public. This situation, to me, is a sign of overconfidence among Google workers about their abilities.
From what I hear, it's the internal performance evaluation and promotion processes at work here. People are rewarded for "launching" products. Once a product launches, backs are slapped, promotions are had, and everyone moves on. There are no clawbacks if the project fails; the fact that it launched is all they care about. This is why there are so many little projects which launch, flounder and then are turned off.
> The problem with this reasoning is that the numbers will start to look a lot less practical if we consider the total number of projects Google has shut down. If we applied this reasoning each time, they'll be out of cash a lot sooner than your estimate.
This should not be true and if it is, it’s just further indication of a problem.
I said 1 ten thousandth of cash on hand for 1.1 million years to drive home how much of a paradigm breaking amount of money they have.
They could make a blank rule that every app gets 20 years of maintenance and support and support 55,000 projects for 1/10000 of their budget.
Now realistically I feel your comment is still missing the point because it’s not even about saying they should maintain these apps anymore.
It’s about the fact that your hard earned dollar is a a drop in the bucket for them. Literally.
Imagine a bucket holding a bucket of water.
Imagine 1.5 million of these buckets back to back.
$1 of your money, is one drop in all 1.5 million of these jugs for Google.
Now pardon my visualizations here but I find it helps when you’re talking about such stupid amounts of money, to help put things into perspective.
They don’t care about services unless the returns are going to be astronomical in one dimension of another.
-
Every service they make like a VC backed startup on their Series A... except they go and attach literally the biggest name in modern technology to it, which lulls people into a false sense of security and also expands the reach of these projects so that them shutting down affects many more people than an early stage product shutdown should.
The app never exited Beta. I would think Google realized there is no $ in being second social network in its category (after nextdoor) at Google Scale.
I do think it make sense for Google to shutdown the app. Spinning it off as a startup, I doubt it is a viable option considering how tied they would be with other Google internal resources.
The point here is that very few people are using Neighbourly to make it interesting to Google.
Btw, in these days I learned that Duo is still alive. I thought it was dismissed time ago. The page on Google Play says 1B+ installs and still I don't know anybody using it. I mean, nobody ever asked me to make a call using Duo. Everybody is using WhatsApp or Skype for that on mobile. So, to get to the point, very second (or probably, fourth, fifth, etc) in the rankings but not dismissed by Google. I think they value our as strategic. Neighbourly was not. They already have Maps.
> Btw, in these days I learned that Duo is still alive.
Duo is great actually, me and my family use it all the time. WhatsApp video calls are pretty bad imho, they tend to show a lot of artifacts and not be very fluent in general. Duos on the other hands looks pretty good, no matter if you're on WiFi or 4G.
The biggest benefit however is the fact, that the user interface is so incredibly simple. For apps like WhatsApp video calling is just an secundary feature, for Duos its the main focus. I never had to explain anything about Duos to my parents, but they still know how to use it with me and their friends.
However, I don't feel like Google is putting a lot of effort into bringing Duos forward, so I wouldn't be surprised if they'd shut it down as well.
(Also, the high install count is probably just because some devices come with Duos preinstalled, although I don't know when its counted as an install in the PlayStore)
The best feature of Duo is that it is cross-platform: you can make video calls between Androids and iPhones (which you can with WhatsApp also, of course, but WhatsApp's video call quality is not that great).
Tot cost of a more reasonable scenario- a single employee, total cost 500K per year. For 10 years this would be 5M. Which is indeed less than 1/ten thousand cash on hand.
Maintenance cost is not flat over time. What happens when a product is easy to maintain (one engineer) but suddenly critical infrastructure gets deprecated and now the transition is going to take five engineers? Do you allocate new resources to support products that already have so few users that they only justify maintenance mode?
I would also suggest that the people who like such a product (neighbourly.co.nz is popular with the Boomers) are not the people who like downloading apps that could be websites.
So yeah, it didn't get as popular as Google would like, but then, how hard did they try?