6 Comments

Beta page launch! What is my new page missing?

by parhelion

https://www.getlightfront.com/

I'm starting the beta for my latest project! I put together a small landing page to gather signups. Any feedback?

My intention with this landing page was to answer the following questions:

Do you get a good understanding of what the product is?
Is the problem being solved clear?
Is the call to action easy to follow?

Thanks!

parhelion

posted to

Landing Page Feedback

on August 9, 2020

Say something nice to parhelion…

Post Comment

2

Wonderful idea, i think there's a real market for it.

Here's the problem:

I'm a developer (your target audience) and It took me a minute of poking around to really understand what you do. You should make your landing page much clearer and immediately tell me what you do.

You should have an email capture form immediately on the landing page, i shouldn't have to click, wait a few seconds for your page to load, and then enter my email, and then click again. Gotta make it ridiculously easy for me :)

Overall I see the potential for your product but your landing page doesn't do it any justice. You gotta think (How do i explain to the user what my product does immediately).

I received the same feedback im giving you a few months ago from someone on IH and immediately applied it to our home page on Stock Alarm and it worked like a charm!

yahiabakour

·
4 years ago
·
Reply
1. 1
  
  Great points! I'll move the email form directly into the landing page to speed things along.
  
  I'm brainstorming how to phrase it clearer, any ideas would be greatly appreciated!
  
  parhelion
  
  ·
  4 years ago
  ·
  Reply
1

it's half decent, due I still wonder about a more targeted user... like APIs are so many things...

key management, webhooks, and activity logs

does this help me?....

Like is the idea that I can develop an empty API and you would wrap EVERYTHING for me? like including payments for example?...

I write a function and connect it to this service and it's automatically a full app?

Powerful Key Management
With Lightfront's deep scoping features, your users can provision keys to fit their needs, or let Smart Keys handle security automatically.

So who manages users? sounds like me... but than users management already needs cred. work, so why should I split off key management (could be that I just wasn't so deep down the rabbit hole before. might compare it to lets say a github personal token management to make it easy to grasp?)

Keep your users up to date with built in webhook support. With Lightfront's simple API, deliver JSON metadata to your users securely and easily.

I'm super confused, the webhook is to the user? what is it?..
I think here your trying to make it more specific, to an async API service, like doing some ML/AI/... something that takes a while.

hatkyinc

·
4 years ago
·
Reply
1. 1
  Thanks for the feedback!
  
  Like is the idea that I can develop an empty API and you would wrap EVERYTHING for me? like including payments for example?...
  
  Not everything. My goal is to specifically target the touch points between your API and your user. Payments are mostly handled by Stripe so injecting another middleware service is mostly useless.
  
  So who manages users? sounds like me
  
  Correct, you would manage you users. The reason for splitting off key management is because there are quite a few things involved with doing it properly that can be quite a pain:
  
  Users should be able to scope keys (by IP address, by resource, etc).
  
  Users should be able to track key usage.
  
  Users keys should be securely stored and be able to be expired, rolled, etc.
  
  These aren't insurmountable issues and it may not be important to you to even need all of these for your API, but they are great to have in a good developer experience. So just like you would consider using Firebase or Auth0 to handle user auth, you could consider Lightfront to handle user API interaction.
  
  the webhook is to the user? what is it?.
  
  Webhooks are to the user. They are ways for the user to subscribe to specific events. You as the developer can configure specific events and fire them whenever, and Lightfront will deliver them the the appropriately subscribed users. If you've used the Stripe, it's pretty similar to that.
  
  So the main value prop I think is that you get a bunch of awesome developer experience aspects in a turnkey solution that your users can directly manage. Hope that helps. :)
  parhelion
  
  ·
  4 years ago
  ·
  Reply
  1. 1
    
    I'd suggest you niche down the offer.
    Like either try to market it directly to a submarket like ML or something.
    Or align with some API generator/lib/helper/service/framework...
    Either of these would focus you more on specific user issues to solve and would help sell it to a specific set of users.
    (even if it's mostly a marketing thing and you'd have multiple marketing streams and one product...
    like if this gets to the point of add "require x" and save this settings file, it's easy in..)
    
    hatkyinc
    
    ·
    4 years ago
    ·
    Reply
    1. 1
      
      Yeah that's a great suggestion. I currently have an API to handle everything, e.g. validate this key, fire a new event, etc. I plan to wrap those in language specific wrappers such as a Node pacakge so that it's as simple as:
      
      const lightfront = require('lightfront') // ... const user = await lightfront.validate(request.key)
      
      parhelion
      
      ·
      4 years ago
      ·
      Reply