As the person who designed and fought for this app, I am a bit sad about the change.
The native app was by no means perfect, but it felt like a real productivity tool that was trying to be respectful of it's environment.
I've come to the conclusion that native desktop apps are just not viable from large companies, even if there is headcount.
WhatsApp native app replaced with web wrapper news.ycombinator.com/item?id=4…
Drew Mochak
in reply to Drew Mochak • • •Matt Campbell
in reply to Drew Mochak • • •Drew Mochak
in reply to Matt Campbell • • •Drew Mochak
in reply to Drew Mochak • • •Drew Mochak
in reply to Drew Mochak • • •Drew Mochak
in reply to Drew Mochak • • •Drew Mochak
in reply to Drew Mochak • • •Drew Mochak
in reply to Drew Mochak • • •And I'm sure there are many others that I'm forgetting.
Matt Campbell
in reply to Drew Mochak • • •Drew Mochak
in reply to Matt Campbell • • •Talon
in reply to Drew Mochak • • •reshared this
Jonathan and Andre Louis reshared this.
Talon
in reply to Talon • • •Jonathan reshared this.
aaron
in reply to Talon • • •Drew Mochak
in reply to aaron • • •aaron
in reply to Drew Mochak • • •@talon @matt I agree, if the features are there, then all platforms should keep up with them. I just don't think the features need to be there in the first place.
counterpoint: those thousands of people wouldn't use the feature if the feature just hadn't been implemented in the first place. Not every app needs to serve every demographic.
Drew Mochak
in reply to aaron • • •I mean, if it was my app, I would never have thought something like Statuses needed to be there, but they are. I also wouldn't think we need a biz app. Or AI. And now I don't even have an app because I didn't think of how to make it sustainable and I had to shut it all down due to the hosting cost. I shouldn't be trusted to make an app that scales to three billion, is what I am saying.
@talon @matt
Drew Mochak
in reply to Talon • • •@talon @matt I think what the post is getting at is that the nature of large companies necessitates making financially motivated decisions over what may be preferable from a technical standpoint. In this case, someone saw that the app was "stagnating," IE not keeping up with the pace of feature development on other platforms. This was seen as a problem, with a solution. It's not the only one, but when you are a mobile app with one team that knows c# and another team that knows JS, you're gonna make your C# devs migrate to JS, not the other way around. JS is easier to hire for, easier to build for and works crossplatform.
A smaller company could say, "we want a simple native app experience so just go to the phone for the other stuff," and deal with the churn, but that's not an option when growth is prioritized by upper management and you have already grown huge.
Jamie Teh
in reply to Talon • • •Dennis reshared this.
Drew Mochak
in reply to Jamie Teh • • •@talon @matt
Jamie Teh
in reply to Drew Mochak • • •Drew Mochak
in reply to Jamie Teh • • •Drew Mochak
in reply to Drew Mochak • • •André Polykanine
in reply to Drew Mochak • • •Drew Mochak
in reply to Drew Mochak • • •aaron
Unknown parent • • •