SimpleOTP

OTP and "magic sign-in link" auth for your website

August 6, 2023 Created a landing page for SimpleOTP

Created a landing page to try to gauge interest in SimpleOTP. Always better to avoid writing code before gauging whether or not there will be interest in the product, hence building this landing page. What do you think? Is it clear enough? https://simpleotp.com

Benjamin Katz

3 Likes

4 Comments

Say something nice…

Post Comment

1
Here we go, hope it helps.
1. Remove or change the animation. If you have to have it use it, do so subtly and not on the entire text block, its amateur hour if the entire page transitions.
2. Your H2 is too long; you don't need to write "passwordless" and magic sign-in link in the same sentence.
3. Change Signup to "Get on waitlist", I assume your product isn't ready yet.
4. Add images of what the user might expect once the service launches. You can transition in these images.
5. Add a FAQ outlining some fun facts about your service/ benefits of using your service vs the "other way"
6. Why should someone trust you with their users email/auth services?
I do understand what you're trying to offer, but it is not clear if you are offering an Auth As A Service like magic or auth0 , or just OTP. Where is the data stored, etc, security would be my top concern with registering with a brand-new service. If I can run on my own servers, is there a github link to some validation etc?

If you make the service easy enough OTP s may be useful for verification of identity, but a thorough explanation maybe needed above the fold.
Rishi_Uttam

·
3 years ago
·
Reply
1. 1
  Thanks for the feedback!
  
  Looking at this, agreed that there's probably too much animation going on. It was a default on the landing page builder I'm using but I'll fix it today.
  
  This has been fixed.
  
  Will consider this, but I think "Signup" is better in terms of wording. My thought process is that it takes up less space and gives me confidence that people would really sign up for the product if it was ready (you're right, it isn't)
  
  Good idea, working on this today.
  
  Same as 4, working on it today.
  
  That's partially why I mentioned self-hosting as a possibility. People are free to use wireshark to inspect network calls if they think something fishy is happening or don't trust the service. To your point about a github link, I probably wouldn't consider open sourcing this but I would consider doing something like what Retool does (they provide a dockerfile and require you to apply a license key if you want to run it in a self-hosted fashion): https://retool.com/self-hosted/. In terms of code examples/how to integrate/install script the for self-hosted version though, I do plan to put those things on GitHub.
  
  In terms of offering: authentication using OTPs (in the form of magic links which I see as a form of an OTP, sms messages with a special numeric code in them, etc). That's what I'm trying to provide here but I'm now a bit worried the landing page is too unclear, let me see if I can fix the wording. It is an interesting point though that I could pivot to just offering OTP verification as a service. Not sure what people are more excited about.
  
  Thanks again for your comments, very helpful!
  ben_makes_stuff
  
  ·
  3 years ago
  ·
  Reply
  1. 1
    
    @Rishi_Uttam fixed #1 (removed all animation except the hover animation on the buttons). Working on the remainder of the feedback today.
    
    ben_makes_stuff
    
    ·
    3 years ago
    ·
    Reply
    1. 1
      
      @Rishi_Uttam #4 is fixed. For #6, I've reworked the website and added some features that are (hopefully) value adds for people wondering why they should pay for this. It took me a lot longer than I expected to rework the page, add screenshots/text/get everything to align properly. Will work on the FAQ part (your point #5) when I wake up! Thanks again for this detailed feedback.
      
      ben_makes_stuff
      
      ·
      3 years ago
      ·
      Reply

About

People