Marceau here, founder of Meemaw. I was working on a different project (communities with better aligned incentives) for which I needed users to have access to a crypto wallet. I couldn't afford users to have to deal with private keys and what not, and I did not feel comfortable being locked to a non-transparent third-party provider for something as important. So I built an internal "wallet-as-a-service" around audited librairies. I dropped the original project since then and that service evolved into Meemaw.
Many "web3 projects" would be better off without any web3 component. But if you do need your users to have a wallet, there are a few good reasons to use something like Meemaw:
- great UX (no faffing around with private keys or seed phrases, easily customisable)
- great DX (get up and running quickly, integrate with your existing system easily)
- more secure (MPC)
- low dependency risk (you've always got the option to self-host or export existing wallets)
If you'd like a refresher on MPC wallets or Wallet-as-a-Service, I did my best to explain it without BS industry jargon: https://getmeemaw.com/blog/mpc-wallet
If you have Docker and Node installed on your machine, you can have a full example running in less than 5 minutes: https://getmeemaw.com/docs/getting-started
You can already self-host Meemaw, and there will soon be cloud hosting as well, with the option to easily switch from one to the other at any time.
The closed-source competitors are all (very) well-funded, but I think we can provide a better developer experience with higher security and reduced dependency risks. Right now, Meemaw is probably not ready for production, but we'll get there sooner rather than later. Your feedback would be greatly appreciated to continue moving in the right direction :)