Thanks for the feedback, I totally agree with this. We often see this mindset but its a matter of education or push the product from non-technical teams.
That’s a typical feature you can add to your signup flows: asking where did you hear about us, the user role, etc. To better qualify users and focus on the ones that matter: triggering email sequences, displaying different walkthroughs, etc.
We’ve noticed that before and that’s a situation, unfortunately, a bit out of our control. Sometimes we try to request those blacklist sites to remove sdk.arengu.com but without much success.
Allowing developers to host the asset would be a workaround, but that can end up with unexpected issues when we update it. We already had in mind the DNS approach but still analyzing potential security issues before moving forward.
Thank you very much for the feedback and if you want to give Arengu a try, feel free to ping me :)
Yes, you can replace those plugins with Arengu and make it reusable across different sites or technologies. Happy to chat when you want to give it a try!
Gold integrations are Salesforce and Hubspot. You’re right we will clarify that as it’s a bit confusing.
Regarding USD we’re supporting it in the next weeks :)
This is a really interesting use case. If you use Stripe, you can use the Stripe Customer Portal to allow your users to handle subscriptions, update users' information, billing details, etc: https://www.arengu.com/tutorials/passwordless-authentication...
Anyway, there are many boilerplate SaaS blocks that might make sense to explore for Arengu, but currently we're focused on signup and onboarding flows/screens.
I get your point and yes, a basic sign-up or login flow can take a few hours to code using a framework. But when you start adding features like OTPs, social login with account linking, conditional logic, data validation, 3rd party widgets to verify identity or link bank accounts, automations to send a welcome email, store the data in your CRM, etc. And as you grow, more things come up and that's when this starts to get messy and most of the time you regret reinventing the wheel.
I think only the welcome email is really valuable to have from all the things you listed. And if you can't handle few ifs within your sign in logic... good luck with your business logic.
I can attest to the pains of working with a complex onboarding flow... At my job, we have about 30 different paths the user could take depending on their usecase. And it's not modeled as 1 30-prong fork that everyone routes through, it's forks that lead back to other steps, skip steps, get data from elsewhere, etc.
The difficulty is that it's typically the product and marketing teams who need to understand the flows the most, in order to understand the conversion metrics and how to optimize, yet they have almost no visibility into the actual state logic that dictates the flow in code. Giving them more control over control flow is a huge win
