Landing Page Feedback August 13, 2020

Feedback on landing page

Quaresma

Hello!

I've been doing some changes on my SaaS product and one of them was on landing page. I'm trying to make the message clear enough and emphasises the sing up, any feedback is appreciated.

https://logre.io/

Thanks for your time!

  1. 3

    Hey Quaresma,

    At first glance, I'd ask myself what are these logs? For logging events, data, for server/client-side, etc. I built one myself so I can quickly understand

    I'd suggest making the header a bit more clear, or using a short description.

    Overall, I love the simplicity, with the demo 👍

    1. 1

      Thanks! That is interesting, I didn't thought on made this too specific(event, data, etc)... I mean, you can log anything you think it is valuable. Do you know what should be the biggest differences for these log types?

      1. 2

        At first, I would actually think it was something related to logging in development (i.e console.log in JavaScript).

        Since it is a data logging service, how about using the term "data logging", or "data logging service"? It would be clearer in my opinion

        P/s: I realized that @ugn has the same question as I do

  2. 3
    • Easily monitor your application, Setup logging with one click
      So it's "only" a log manager service right?
      why not only talk about that? it doesn't "monitor" it's a useless word in this context.
      if it's a super simple service, it should be super simple page and statement
      Some inspiration https://www.papertrail.com/
    • Why are the example of sending logs? not replacing a logger in an existing framework?.. I'm not going to copy this to every log line in an app, just no.
    • I'd rather have the code samples on that same page with a tab style design, not open new pages... it's simple isn't it?... the linked github code samples belong in some docs section
    • Spanish mixed with English? :narrow_eyes: (main screenshot)
    1. 1
      • I updated the main title to be more direct.
      • Sure, have to send logs manually is not the ideal. This is a working in progress and we already have a library for apollo graphql and express. I hope to do that for more other frameworks in the next weeks. Do you have suggestions?
      • I totally agree with the tabs design for the examples.
      • I took this from a real account. Since this project in specific is based on Brazil, the box name is in portuguese. Do you think this is a problem?
      1. 2

        I updated the main title to be more direct.

        I like it way better :)

        Sure, have to send logs manually is not the ideal. This is a working in progress and we already have a library for apollo graphql and express. I hope to do that for more other frameworks in the next weeks. Do you have suggestions?

        Golang has logger libs and it's pretty standard like one class to inherit and it would be useful for all..
        ROR is a big one

        I took this from a real account. Since this project in specific is based on Brazil, the box name is in portuguese. Do you think this is a problem?

        very low fidelity thinking this would polarise a little, US guys would look at it negatively, 2nd language speakers would like it, can be expended upon for the 2nd group further
        If you get to a/b test it on a big crowd let us know ;)

    2. 1

      Thanks for the precious feedback.

  3. 2

    Hi, here is my feedback! (Kind of similar to what others are pointing out)

    It looks like a product for developers, DevOps.....

    • "Log", what log exactly? Log can be console log, server log or error logs

    -The 'above the fold' of your website is where you make it. Keep in mind people are super busy on the internet(their minds are already distracted or irritated while they are looking at your webpage)
    -So within seconds they land on your page, they SHOULD get a CLEAR CUT IDEA of what core value you offer(and not confuse them, like what happened here)

    • Once you get their attention with your value(heading), they will consider scrolling down for more information

    -Overall, I liked the design!
    -Try adding short and sweet demos as GIF (this is powerful!)
    -Don't try to replicate what the competitors are doing, try to be as human as possible!
    -Don't assume that visitors will get it
    (Devs and Engineers are humans too, they also tend to get confused)
    -'Start without sign-up' - I like that. Getting your audience to try out the product before asking for their info.

    If you would like to learn more on how to write effective headlines search for 'Unique Value Proposition'

    1. 1

      Hey @johith thanks very much! I will take a look on 'Unique Value Proposition', I didn't hear about this before.

  4. 2

    It says "Start free", but where are the pricing details? I don't want to engange with a product if I don't know how much it's going to cost me later.

    1. 1

      Yeah, definitely. I'm working on that!

  5. 2

    My first question after I opened your page: what kind of logs are you talking about?
    Since it's a tool for developers, maybe you could give some examples and specific use cases. Good luck!

    1. 1

      I made this to be generic so developers could log anything... Do you think be more specific could be good?

      1. 2

        Most of your customers will not want to "log anything". They will have very specific problems. Can your product solve those problems? Show it.

        1. 1

          Do you think "data logging" is a good name?

          1. 2

            Good name for what? :)

            BTW, what are those links at the bottom of your page? There is no title for that section, no description.

            1. 1

              For this question " what kind of logs are you talking about?".

              "BTW, what are those links at the bottom of your page" 🤔 what links?

              1. 1

                No, sorry, "data logging" does not explain anything, really. You need some examples, use cases. Maybe even names and photos.

                Please disregard my comment about the links, I understand now. I was talking about "Javascript", "Express JS", ...

  6. 2

    Maybe you should explain a bit more about the features!
    I could just see that you are providing an SDK/API to send logs. But what after that?

    • Dashboard
    • Charts/Visualisations?
    • Inferences?
    1. 1

      Yeah, right now there is only a simple dashboard like the home page image. I'm trying to get more users and more feedback about what should be the next features.

  7. 2

    Biggest ones for me were:

    • What's the catch? Where's the pricing info? I rather pay for something my infra depends on - I've seen heaps of indie products die after offering free accounts.
    • Needs more UI screenshots. I want to see how filtering works. Even videos will do.
    • Needs a list of features. Just a simple list of what's being offered is good enough.
    1. 1

      That is true, I put these on my list! Thank you.

  8. 2

    The landing page is clean and simple. I like it.

    Yet it is not clear at all what the "monitoring" features are. Here are the questions I have in mind.

    • Does it just store logs? (this is the only visible feature on the page)
    • Does it trigger notifications on custom events?
    • Does it allow complex searches (filter, joints, nlp)? With what languages?
    • Does it support log rewriting?
    • Does it render visual reports?
    • Does it include dataviz capabilities to allow the dev teams understand what's going on?

    You can get inspiration from https://www.loggly.com/

    1. 1

      Yeah, right now this only store logs and provides some filtering capability. I'm trying to get more users to get more feedback about what should be the next feature... however, I don't know if this is the best strategy.... thoughts?

  9. 1
    1. There is no pricing section.
    2. The login page highjacks the back button.
    3. (Dashboard) The text search filter should be visible without clicking "Filters" first.
    4. (Dashboard) Log interface looks very simple, I am not sure how usable it is compared to something like Sentry.
    5. What kind of logs is it best suited for?
Recommended Posts