mhamann

I love that thought!

I think they often do, yes. But I feel like there's often a decision point there for the user. The thought "if I don't create an account, but need to come back later for something (status, returns, questions), can I still get what I need?"

Rownd would essentially eliminate that mental question entirely. You provided an email or phone, therefore you're more than just a guest.

Apologies for the confusion. The pricing is monthly, but we're lowering it to $49/mo for anyone coming from Hacker News.

I'm a huge fan of self-service as well. Picking up the phone to call someone is like...the last thing I want to do. So 1990s! :-D

We're hard at work making Rownd much more self-service. We'd love to hear more feedback once the process there is a bit smoother!

Sent! Thanks for helping out!

Great point! Thanks for the observation. Unfortunately, at the moment, we only have the client-side handlers built, but we do plan to add support for server-side rendering in the authenticated state.

For now, you can use our `is_initializing` flag to wait until the authenticated state is fully loaded before completing the render in the browser. I realize that's not an optimal solution for this use case. We'll get there!

We're fans of SOLID too! I think there's a ton of interesting work to be done in that space to make it scalable, secure, and really user friendly. We've definitely had some discussions around how Rownd and SOLID might fit together, so stay tuned.

From a browser perspective, Javascript needs to be enabled.

We'll definitely release an SDK for Go! We're heads-down building SDKs for all sorts of technologies, and could actually use some engineers with a background doing that sort of thing. If that's you, I'd love to chat about it (mhamann@rownd.io)!

The pricing is monthly, but if you're interested in more of an annual thing, reach out and we can get you numbers with the annual discount applied. We're working on more self-serve options, which will eventually include the ability to subscribe annually right from the website.

Thanks for reaching out! We have a couple of positions that we'll be opening up soon. DM me over on LinkedIn (https://www.linkedin.com/in/matthamann/) or drop me an email (mhamann@rownd.io) and we can chat further. :-)

xD

Pesky email providers thinking everybody wants to track everything all of the time. Sheesh!

Thanks for the feedback! Sorry that things weren't clear! We'll work on that...

Yes, once you've added information to one Rownd partner, it _can_ become available to a second partner, but _only_ if the user consents to sharing it and only when the fields/data types match between the two apps. Typically, that occurs during the sign-in process.

We currently require verification on each partner site to ensure that the person signing-in is actually the holder of the email/phone. In the future though, we plan to allow a user that's authenticated at one Rownd partner to click a single button on a second partner site to simply pass the existing verification and account info across. In that case, no email/sms is needed as long as its done in the same browser/device.

Thanks for the question and your support!

Sorry it didn't work for you! Do you happen to be using a service like Pihole, etc to block specific domains on your network?

We currently use Postmark for sending transactional email and by default, they rewrite all links to use their tracking servers. We didn't intend to have that enabled, so apologies for the oversight. I've just disabled that option, so links should resolve to their intended destination now. Links that go through multiple tracking redirects are a personal pet-peeve of mine as well!

Thanks for the support, Chris!

Hey, thanks! There are a number of companies working in this problem space, and certainly Userfront is one. But one of the most obvious differences is that the first thing Userfront does is ask you for a password. We'll never do that because we firmly believe that passwords are essentially a Web 1.0 construct that needs to disappear forever.

That said, we're not just authn/authz software. We're helping companies improve their UX across every facet of their web and mobile presence. We focus on how account data spans various systems, not just isolated within one datastore. We also consider how user data flows through various UIs, is part of personalization, etc.

At the end of the day, we want to make the relationship companies build with their users more akin to how it works in real life. It's often a conversation, not just a transaction.

Great feedback! We'll definitely work on improving that.

Thanks for the heads up! We've fixed the link!

We envision a future without passwords and where you can take your identity around with you and plug it in wherever you want, while also maintaining control of that personal info. Interestingly, the first thing clerk.dev asks for when you sign up is a password...

Additionally, we don't think you should have to have a React/Vue/Next.js/etc site just to add auth. We want this to be plug-and-play anywhere and work across all of your web properties (and eventually mobile too). That could make the marketing, docs, and support experiences better at so many websites with a level of integration that used to take weeks or months to build (if anyone even bothered).