Landing Page Feedback October 20, 2020

Do Full-Stack developers understand my product? (Experiment)

Adam La Morre @alamorre

For the three months, I've been building a project specifically for react developers.

I don't want to spoil my experiment by describing it, so heres the link:
https://chatengine.io

If you build websites and servers, please let me know if you get what I'm trying to do.

Thanks a million, IH'ers are the best ♥️♥️♥️

  1. 1

    My understanding is that it's like Intercom.

    Some initial thoughts:

    • not sure what Connected server means
    • also I expected those titles (Great documentation etc) to be clickable – guessing you're planning to add links later on since it's WIP.
  2. 1

    Hey this looks great and useful and I think I get what it generally does.

    Specifically I really like the live demo and code example which explain well what to expect and how to use!

    I've only taken a quick look, assuming that what you wanted, so sorry in advance if I'm missing something important but here are some things I'm not sure I understand:

    • "Connected Server"- I'm guessing you mean it has its own external server and I don't need to host anything on mine (?) but I'm not sure I'm familiar with this exact phrasing.

    • "Syncs with your database"- didn't understand exactly how (or why)

    • "userName", "userPassword" props- are these the app's or the end user's? If it's the former, maybe it's better to rename them to be more clear. If the latter, I'm not sure I understand how exactly the end users sign up in the first place.

    My 2 cents, hope that's helpful :)

    1. 2

      Thats a great reply!

      This is useful because I can tell you know what you're talking about so the confusion probably comes from my wording. I'll look that over 👍👍

  3. 1

    I can create a chat box on my website by just copy-pasting the code, and some minor config. But it's for React apps only.

    1. 1

      I would say that's 50% correct which is my fault.

      I'll probably add sections for common use cases to make it clearer 👍👍 Thanks!

    2. 1

      These are my thoughts exactly!

  4. 1

    I follow this rule when writing website copy:

    1. Who: who is your target market? are you targeting core developers or ordinary website owners?
    2. What: what problem does your service/solution solve?
    3. How: How does your service solve the problem in (2)?

    The general rule is for your web copy not to list features but solutions. Put yourself in the shoes (mindset) of your target customers.

    My 2 cents.

    1. 1

      Thanks solution first phrasing is a good idea. Funny i never thought of it that way...

      Thanks 👍

Recommended Posts