Signups are the gateway to your product. Often times, you need non-technical team members to be able to experiment and iterate with them. This type of work is often boring work for the engineering team.
One immediate thought for a feature (you may or may not have already thought of this...). A picklist of options for "how did you hear about us?"
That will help marketing and sales to get more granularity than the usual 80/20 split between "referral" and "direct" in Google Analytics. With all the brand-building efforts like newsletters, videos and podcasts going on - traditional "last touch attribution" tools like Hubspot or even multi-touch tools like Bizible don't capture brand.
Thanks for the feedback!
Of course this is an edge case, your company can't reasonably be expected to cater for how people on the internet decide to filter content on their personal networks, and the majority of people won't run their own DNS servers & take the same slash and burn approach to whitelisting as I do, so I understand if it's seen as a non-issue or rare edge-case.
I'm guessing the SDK URL got flagged on the list because the form builder has been used by some websites for various marketing related purposes triggering a blacklist maintainer to blanket ban the URL (I've had to whitelist common things like cdnjs for similar reasons).
That's fine for marketing forms / flows, but I'm thinking since a website or application's login is more of a primary / critical feature it would make me think twice about using the service if I were designing an app aimed toward tech & privacy savvy developers.
As a workaround, does your service still work if developers decide to host the needed assets on their infrastructure or proxy them under their own DNS? Could be a way around it.
Anyway the feature looks interesting, login flows are far from trivial once you get into the area of social login, OTP, device authentication, 2FA etc. I'm hammering out the architecture of a SaaS service at the moment so I can appreciate the niche you're trying to hit, good luck with the launch and hopefully the above feedback is useful.
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 :)
On the pricing page (/pricing), could you support USD? Also, what are "Gold Integrations"? There doesn't appear to be an explanation but it's listed for every pricing tier.
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 :)
Thanks for the feedback and questions!
A feature request: I would absolutely love to have something like Arengu that also handles the rest of the boilerplate SaaS stack. Key is a branded user portal with a billing area (I should just give it my Stripe keys and let it generate the screens); user/team management, etc.
To give an example: if you click your avatar in the top right of a Github page, I would like to outsource all of those pages. (How would that work? I would provide APIs and then have some kind of page builder in Arengu that would display the data & handle user input. So for example if I were Github, I would have an endpoint that would return JSON for the repositories for a user, and Arengu would display github.com/$USER?tab=repositories. There could also be API contracts where my API essentially returns the HTML for part of the page.) Basically -- use your front-end builder to reduce the front-end code I need to write & manage.
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.