2
3 Comments

Landing Page Feedback For API Management Application

Hey IndieHackers!

It is my first time posting here (and building), but I have already been inspired by the work of many community members here!!

I'm building a API management Application(can create and manage API with no code for back end) that I am about to launch -- so I would greatly appreciate any feedback regarding my landing page.

Landing page : https://fireapis.com/

Thanks!

on January 24, 2021
  1. 1

    The biggest anxiety (cost) is about the future viability of this platform. "Will it be around for a long-time? If I build on top of this, will I get burned?"

    I'd try real hard to reduce that anxiety, which will add appeal to your product.

    One of the ways that will actually re-assure buyers is by showing a solid public price. Pay only when you ship. It's 150$ a year, upfront.

    To go further, I'd add a personal plea: "We take our uptime seriously, and we build our stuff on own apps of top of this platform. We're planning to be around for the next 5 years or more, and we're doing that by charging a fair price, and keeping our costs down. We won't be building every feature, because we'll concentrate on the long term."

  2. 1

    Hi,

    I'm Indie Hacker with a backend developer background. I was thinking multiple times about creating something similar :D

    The site is pretty. Good job with HTML and CSS ;)

    For sure, your main header and subheader should be more catchy. I'm not a content specialist, but for me, "Build APIs with no-code" sounds better. It tells more about your product.

    I'm not a native English speaker, and I use Grammarly to increase my English grammar skills. I see many small bugs on your site, missing spaces after a comma, missing dots.

    As a backend developer, I would like to know more about security, how authorization works. Is it possible to validate gotten data?

    I was working on https://sheetsu.com/ - it's quite similar, you can save and read data by API, but you can also read and edit data at a spreadsheet, and it was the most valuable features for our customers.

    I like the idea, so good luck!

    1. 1

      Hi devhulk,That's a really good point! I'm definitely planning on improving the grammatical mistakes.Basically every environment will have seperate JWT client token and for every API created in specific environment has to be consumed using client token in header.Yes,as of now currently working in validation of data sent using APIs,it will out with beta product launch.

      I value the insights and guidance you provide.Thank you for your assistance.