91–100 of 110 posts
You enter your email, get taken to a page that tells you to open the email. If you close that page then you can't login even after clicking the link in the email as you need to leave that tab open, open a new tab for your email, open the link in the email, close that and go back to the original login tab.
Why can't you just click the link in the email and you login?
In terms of the pricing, it may be worth considering a cap (e.g. 5% on successful payments up to a maximum of $Y a month), otherwise, you might find that your entire userbase ends up being comprised of early-stage projects that are making little to no money.
If I had some smaller website that I charge nothing or barely anything on, I might. If I had a bigger SaaS product, probably not. I wouldn't say your pricing is necessarily unfair, but paying 5% for what is probably a very small part of the application, I couldn't stomach.
Thanks for the feedback! I’m open to changing the fee – is there a % fee you would be more comfortable with?
Implementing email login on top of that is probably as easy as integrating with an external service, without the risk and the concerns about leaking user emails.
will you be there in 10 years?
He does not have to be there in 10 years. If his service where to go away you just change the login system to something else, there are open source alternatives. The id is the email, so there is no lock-in. That's for the login-part at least, adding stripe manually on top would be a bit more complicated, but doable.
no point or use of this service then, might as well build our own / use oss.
Earlier quoted context omitted.
Login management should be built into the browsers instead. Imagine a UI where you go to log in and instead of a text/email field for login and a password field you get a drop down with a list of your personas that you’ve created with the option of adding a new one. Under the hood it would use a public/private key pair to authenticate you with the site. Browsers could implement a service that backs up your personas a…
Don't browsers essentially do this already? You're suggesting some different backend details, but the UX you describe is already in place.
Earlier quoted context omitted.
Login management should be built into the browsers instead. Imagine a UI where you go to log in and instead of a text/email field for login and a password field you get a drop down with a list of your personas that you’ve created with the option of adding a new one. Under the hood it would use a public/private key pair to authenticate you with the site. Browsers could implement a service that backs up your personas a…
> Login management should be built into the browsers instead. I would go even further than this, and say that a cryptocurrency might be among the best ways to build a universal login system. Imagine an Ethereum-like coin where the wallet is the username, and you spend the coins while authenticating, gaining privileges, and the blockchain stores your public info like a username and avatar that you can bring to any web…
If I had some smaller website that I charge nothing or barely anything on, I might. If I had a bigger SaaS product, probably not. I wouldn't say your pricing is necessarily unfair, but paying 5% for what is probably a very small part of the application, I couldn't stomach.
Paying a fixed fee might work, but if you start charging per single user, it's problematic. I can see some value if it's per bundle of users (e. G. Every 10 users the pricing increases)