Now add the cost of providing support (it's a paid product now!), payment handling on their end (in a privacy-preserving way, which excludes most common payment methods), and top it off with the immense damage to the network effect by excluding all the users that can't or simply don't want to pay $1/year...
Donations seem like the much better option here.
You don't need to provide support, even much more expensive consumer services live without a proper one, so being explicit about the fact that you only pay for infrastructure could suffice
Not sure why payment privacy has to be so strict for everyone
The network effect damage is real, but maybe it could be limited with donations :)
Just ignoring customer complaints and selling the service "as-is" is usually not an option.
Besides, even now they're not ignoring all the complaints, the do fix bugs?
Maybe to be more specific, how much did it cost WhatsApp when they had $1 price and a tiny team? How does it compare to the cost of SMS?
But I think it's pretty clear by now that this is a feature for FVEY IC, not a bug. FFS, they burned development resources on stickers, but abjectly refuse to offer alternative account identifiers. The standard apologist response is, "but phone numbers make adoption easier". Sure, but nobody is asking to replace the identifiers, or even to make them nondefault. We're just asking for the option. It could be hidden behind a developer mode for all I care, but it should be there.
The fact that they abjectly refuse to do it is enough to tell you about what their true motivations likely are.
I'd like a signal daemon on all my servers for alerting which could message me via Signal. This is worth a monthly fee to me.
I know people running small businesses who would really like to have a business Signal account: an ability to send Signal messages as a business identity without tying it to some specific phone number. This would be worth a subscription even if they had to get their customers to install Signal.
Signal need to figure out what product they sell that's going to fund the privacy objective: because there's plenty and they're worth having.
Just sign up with a Twilio number (using voice call) and you can make your own bot.
FB acquired them next year and if my memory is correct there were 19 in the team then.
IMO Signal need to figure out what they sell to people with the money to say "yes, this service helps me make money" so they fulfill the big mission statement. That's true viability.
Within that bucket there's some real obvious ones: server monitoring and alerting (I have Signal, let my severs have Signal so they can talk to me, maybe at an agreed reduced throughput rate so someone doesn't just try to run TCP/IP over it), and letting businesses have a secure multimedia messaging channel to their clients for notifications.
With just a bit more effort you can see that most of those $148 are not related to the extra customer support we're discussing, but rather to the things that Signal is already doing
Costs and expenses in 2013:
Cost of revenue 53 (payment processing fees, infrastructure costs, SMS verification fees and employee compensation for part of operations team)
R&D 77 (engineering and technical teams who are responsible for the design, development, and testing of the features)
G&A 19
Indeed, the Wire messenger is done like this - it offers phone number, but has an option to not use them and only rely on the usernames (although I think you need to register in the web browser for that)
Besides, the original point was about huge$ from running a paid vs free app, which isn't the case
But yeah, I hear you. It would be nice if it had a official bot interface where maybe all the bot's receipients have to be whitelisted so that it's easy to use for stuff like server monitoring but not easy to use for spamming.