Launched our Product and revised landing page
After 2 years of development in my spare time, I have finally launched Auth Armor - https://www.autharmor.com
The landing page has been up for a few years but I've done quite a few changes for the launch, including adding our new explaining video.
Without explaining anything here about Auth Armor - can I get your feedback on the landing page, the intro video and if you understand what Auth Armor is offering and how it could work for you, if at all?
I really appreciate your time! Thank you!
Trending on Indie Hackers
On a quick look from my limited knowledge:
Color scheme is a bit intimidating. Seems unfriendly which I believe is the opposite of the emotions you aim to provoke. The 'tone' of it is...Heavy ?
"Modern Authenticator app using biometrics and security keys"
COULD be:
"Revolutionary app gets RID of outdated passwords and forgetfulness"
The Headline and Sub headline is too 'techy'. Best copy is plain copy. If this is directed at everyman your UVP is not clear/concise straight away and I don't know what 2FA means. You should HOOK visitors attention straight away on your Above the Fold with BENEFITS. Think of not what IS it or what it DOES but what it does FOR ME. I'd say take to obvious benefits to the front and stress/illustrate them with you HOOK and Hero Image. Just my 2 cents for now I gotta jet. Hope this helps.
Great feedback, thank you!!
Hey Shane,
I took a look at your landing page from my iPhone and it looks good. I understood what your product was from reading the site and the explainer video helped even more. I tried the app out and logged into the portal. It works similar to Microsoft Authenticator which I really like how it just sends me a push to login.
It seems like the pricing would be good for use with an enterprise app but might add up quickly for a SaaS app.
I really liked the explainer video, Did you produce the video yourself or did you hire someone to do that?
Congrats on launching!
Thank you very much for checking that out!
For the pricing - it's something I struggle with constantly. I was quite a bit lower with my pricing at first. Advisors said you can always lower the price, make deals with people, etc, but its harder to raise the price. I'm feeling around and will see what works. I am open to making anything work right now.
As for the explainer video, I hired someone on Fiverr that I've worked with in the past. I produced the script with the help of several friends. However, It takes me months to get it on paper.
Thank you very much once again!
Yes, pricing is hard but I think you are on the right track if you are going after enterprise market. They are willing to pay for a good solution. You could a still end up saving them money over using something like duo which charges per user instead of per auth.
I'm working on offering per user and per auth options. I'm also noodling enterprise vs SaaS, bloggers, eCommerce, etc - and how I can offer something much more appealing for those markets while still charging a premium for enterprise, with things like device management that a SaaS site, for example, would not get or even need. Time will unravel and reveal this mystery - :P
Interesting ... been researching this area for a client project. We ended up building our own 2FA via SMS code. Not the best, but sufficient for our needs. Without a doubt there's a big market for what you're building and it will only grow. My question would be, how will you get people to trust that your app is 100% secure. Whoever decides to consider a tool like this will be heavily focused on security, and then that double backs on a small start up having to prove or convince that what they've built is better than Google Authenticator etc.
Great job in what you've done.
Hey there, Thank you for your feedback!
As for your question on "How will you get people to trust your app..." - well that is the beauty of cryptography! I don't have to prove the app is secure, because the cryptography does it for us. Auth Armor is 100% crypto-validated, end-to-end. Auth Armor does return a simple "true/false" flag for if the message was authenticated, but we also return all the signature data, the public key, the signed data, the signed message and all of this can be independently verified. This ensures security.
You can check out this webpage here: https://fidoalliance.org/
This is an organization that is working to come up with better authentication standards. They do no make a product, rather, they make specifications. Our app uses these specifications and ensures great security for all.
Great question!
Thanks!
-Shane
"Watch our explainer video!" is redundant.
Autoplay video on scroll. It's pretty good.
It really hard to understand where you can use autharmor. Is it mobile apps only? Or regular sites on mobile?
And what is fallback if I don't have needed sensors? Or I should build fallback myself (this in my eyes destroys value prop)?
Hello @slavaGanzin - thank you for checking out the page!
Great recommendations, thank you! You can use Auth Armor anywhere that can call our API.
As far as needed sensors, you don't need any. Everything works on the phone. The way Auth Armor works is you make a auth request to a user of yours via our API. Auth Armor will locate all of the users registered and enrolled devices and send a push notification to that user. The user will then have several options to respond to the authentication request from their phone. This is one of the great features of Auth Armor. There is not hardware to buy. Auth Armor enabled BYOD Authentication. If the users mobile device does not support biometric, then we can fall back to pin on the device, or even use FIDO security keys instead of biometric.
Don't sell to me. Sell it on your page
I would have loved to see a real implemented demo somewhere.
Looking at the pricing: what's a "team-member"? and what's Reporting Retention?
Also, I like the idea but what are the disadvantages other than you have to always have your phone with you?
Hey there,
Can you tell me more about what you have in mind for a real implemented demo?
For the pricing, a team member is someone who can help manage the projects, users, view auth history and more in the organization. Reporting Retention is how long auth reports are kept on hand, such as your users logging in, etc.
As far as disadvantages, I'd like to think there are none. But yes, you would always have to have your phone to login. I feel this is similar to today, with 2FA, and many people have phones or mobile devices where Auth Armor can work. It also enabled BYOD for authentication for the enterprise.
Thanks for checking it out!
like I watched the video...I assumed it doing what I thought it was.
Next, as a developer, where do I go from there? Where's the quickstart?
What's the CTA that I should take? Download the app? Check the docs?
What's the first significant step in adoption?
Check out how auth0 does it. or firebase (https://console.firebase.google.com/)
That's to me personally, the biggest flaw of your landing page....
The "Quick Start" can be found when clicking the "Get Started!" CTA button on the main page. This getting started page has a few guides on how to make your first project, using the API to invite users and then send authentication requests to the app using the API as well.
I'm open for suggestions on what to change. Let me know. Thanks!