The point I was trying to make with the WhatsApp examples is that the work to make it easier could be part of Peepeth. I don't think WhatsApp is leveraging much existing work to do what it does, they've just come up with a good flow that fits their model.

Yes, the challenge for Peepeth is probably greater than that faced by WhatsApp, but not impossible.

The implicit assumption being made in the parent is that the current market size is dictated by UX, rather than something else like a compelling use case for the majority of the population. I'm suggesting that with some UX work and a compelling use case (which Peepeth may or may not be), there is nothing preventing large scale adoption of crypto.

Right. And I guess what I'm saying is that if Peepeth can solve the crypto UX problem, I'm already sold - but I've seen nothing in their page that suggests this is even on their radar. They seem to take ETH for granted - which is kinda' like Whatsapp saying that "you need to install bcrypt, create a public-private keypair, configure your identity wallet to keep the private key, and then you're all set to start using Whatsapp!". You can see how that is not a very attractive proposal - for most users, encryption is completely transparent in whatsapp, they don't even know it exists.

Peepeth could do something like Whatsapp, say "it costs you 1USD/month to use Peepeth, but for the first year we'll waive the fees" and transparently purchase ETH on your behalf behind the scenes. But they don't do that. They put all the crypto burden squarely on your shoulders, with no hint that they'd consider making it all seamless/ transparent for the regular user.

I think having a way to overcome the usability problem is a good idea.

Keep in mind that Peepeth is a self-funded effort by one person (Bevan). I'm sure he'd be more than glad to solve the usability problem, but purchasing ETH on your behalf can't be done without funding or a source of revenue.

However you can donate see https://peepeth.com/support