8
46 Comments

First time building a landing page.

https://ezconsole.dev/

My first ever landing page, I have built this page as a base to try and generate some interest for a tool I built for myself and am looking to turn into a SaaS. I'm no front-end developer but here is my attempt.
Any feedback much appreciated.

ezConsole.dev

submitted this linkon June 25, 2022
  1. 5

    The page looks cool. I have made this video with me reviewing your landing page. I hope it's valuable to you.

    1. 2

      Wow, what a great format for some feedback.
      Thanks for taking the time, it really helped to just be able to watch someone and hear what you were thinking and at what points.
      A fair few things for me to go away and look at I found that very valuable.

      1. 2

        Glad it helped. I often do this kind of feedback whenever the WBE Space showcase a new product and they always find it super useful, so I am glad that you did too.

  2. 2

    I would definitely consider having your main CTA in the top right as part of the nav bar. That way you increase the chances the user will convert by always making it visible.

    I would also consider having a product image or a mock-up. People are very lazy and don't want to read - often an image can communicate what you need faster!

    1. 1

      That's a good idea putting it on the nav bar. I'll be working on some gifs of the product soon. I do think that will really help the page, as you say people are lazy (me included)

      1. 2

        Yep! When i say people I was defo including myself in that too :)

  3. 2

    Let me ask you a few of questions...

    1. What is the problem I (the customer) is trying to solve?
    2. How do I currently solve that problem?
    3. How does your tool make my life better (easier, faster, cheaper)?

    At the moment your landing page tells me this...

    • My problem is AWS tasks (whatever they are).
    • Your solution makes it "simpler" than whatever I'm currently doing
    • To use it I think I need to download your pre-release desktop app to do things I can already do without downloading it.

    Right now I have to work very hard to figure out what your landing page is telling me. There's a pretty good chance I still don't understand it. Even if I do understand it I don't find it a very compelling reason to take the next step.

    So my suggestion at this stage is to try and answer the above questions. Don't edit your landing page just yet. Just try to answer those questions right here and get feedback on the answers.

    Another way is to go back a couple of steps and tell us your story. Why did you feel compelled to create this tool in the first place?

    1. 1

      Thanks for you detailed reply,
      I'll start with the last question,
      Why did you feel compelled to create this tool in the first place?

      So, It all started out when I was working on a project that we wanted to introduce Pull Requests into. CodeCommit does actually support pull requests like most things though it's a bit berried in the console plus based on our configuration I need to jump through a number of hoops to log into the console and get the right account (we have a few accounts).

      Thats when I created the tool to list out all the repositories, you can also favorite repositories, it gives you information like latest commit, number of open pull requests and fairly standard information about the repo, you can also view the pull requests and I'm currently implementing the closing process. I didn't want to replace the git part as there is lots of good options that exist already today but noting can deal with the pull requests other than logging into the console.

      The next thing and this again mostly comes down to the logging into the console being a pain was a cloud formation stack manager, essentially recreating what you can do in the console but with some additions. When you look at resources created in a stack the console has no link to these, for example if I want to see the log for a particular API I need to go and find its long name (CDK generated one) then get into cloud watch and then click, click, click before I'm at the latest logs. What I'm putting in with the tool is ok you can click on the resource in the stack and you have some options, one is view logs and it takes you right there. The options would be different per resource type so dynamodb would take you to a view/edit table ect.

      If I was to go back and answer your questions?
      What is the problem I (the customer) is trying to solve?
      At a high level, the console is slow to access and AWS services are not well linked together
      How do I currently solve that problem?
      By digging around the console until you find what you are looking for
      How does your tool make my life better (easier, faster, cheaper)?
      Easier and faster

      1. 2

        Forgive my ignorance as I'm not an AWS customer. Many of the things you're talking about are over my head. I have used Azure however, so I think I can piece together enough context from that.

        As far as I can tell from your story, your competitors are:

        • CodeCommit
        • AWS console
        • Cloud Formation Stack Manager

        When talking about competitors I like to use the example of a Lawn Mowing business. Lawn Mowing businesses are not just competing against other Lawn Mowing businesses. They are also competing against people going down to the hardware store and buying a lawn mower so they can do it themselves.

        So in your case, you're essentially competing against people doing things the "usual" way. Your job is to show them that there's a better way. Your job is to give them "superpowers".

        Having competitors is actually a good thing. First of all, it shows you that people want solutions to these problems. It also gives you an enemy to attack. You can figure out their weak points and strike.

        For example, I quickly googled "CodeCommit reviews" and found this negative review:

        There is no integration with CI systems in the Pull Request process. My enterprise software development processes require enforcement of a successful build and all passing tests before a PR may be merged. CodeCommit currently doesn't have any webhooks into CI systems to show build status or test results. This is a show stopper for most enterprise development teams.

        Seeing a negative review like this shows that there's at least one person out there feeling simliar pain points. When you're writing your landing page you should use words that talk directly to these pain points.

        From what I can gather, your other pain points include:

        • Merging pull requests is difficult
        • Logging into the console is annoying
        • Managing multiple accounts is annoying
        • Seeing logs for a particular API
        • Repository management

        When it comes to your landing page you've essentially got two ways to go:

        • You can either focus on one particularly painful point
        • Or you can go with a more broad summary of how your tool helps people

        So for example, your headline could be something like:

        Manage AWS CodeCommit pull requests the easy way

        Or something like:

        Never login to AWS Console again

        To be honest, writing the headline is the hardest part. Start with something, but don't be afraid to come back to it when you've figured out the rest.

        But the key thing to remember is that you're telling people how their lives will be better after they are using your product. They don't really care about features, and they definitely don't care much about the technology you're using. Don't lead by telling them it's a "desktop application" or that you're currently in "pre-release". You can add these details later down the page.

        Finally, use the rest of the page to address all the problems you're currently helping with. Remember, think "benefits" not "features".

        For example, what is the benefit of the "Pull Request Viewer"? It might be something like:

        See all your pull requests in one place. Merge them with ease.

        Or the "Log Viewer" might be:

        Find the logs for your API's in one click

        Anyway, I hope that's helpful. I'm not really your target customer so I probably got lots of little details wrong but I think you get the idea.

        1. 1

          Thanks, this is a brilliant reply and has given me a lot to take in.
          Really apricate the time for you to review it in such detail.

  4. 2

    I like it. It's super clean and straight forward.

  5. 2

    Is the tool working? If yes, you may consider adding a screencast/demo video.

    1. 1

      Yes I was thinking of adding some gif's under each feature section (at the moment it has a placeholder image)

  6. 2

    I think you're confused. Honest, unsweetened feedback ahead.

    You took a template, filled in some details, and asking for how is it? Well it won't help you, nor the people looking at it.

    Instead , for a landing page, you should ask for feedback on your idea, your copy, and possibly people would comment on if the page looks ok enough from the sidelines.

    From what I perceive, the domain name isn't good, the copy is not super-convincing, the product isn't clear enough (I can't even tell what you mean by 'desktop tool'.. is it an app?, and will it work on mac?), the feature list is pretty useless and reflects that you don't have much understanding of what people mostly use AWS for, and what problem you're solving.

    On top of that, there is no 'wait-list' form yet so you aren't getting anything here anyway. Overall a low-effort attempt with no flesh to it.

    I apologize if it sounds rude, but I hope it gives you some pointers.

    1. 1

      Thanks,
      I appreciate all the feedback,
      In terms of the feature development, I have been using some of the AWS slack groups and a lot is from my own needs, working with AWS every day.

      Yes I agree with the feature list, I have yet to really populate the feature list and descriptions when you drill down into one from the old site but I was mostly struggling with just getting a page built that looked professional enough for someone to even start reading through it.

      In terms of what platform, it will work on, good catch I did not have that. Its built-in electron so should be good

      In terms of the wait-list, how does this differ from the Subscribe to the Newsletter?

      1. 1

        Wait-list has a completely different intent than a subscription form.

        Btw, I didn't see a form there, seems like adblock just strips it off (I turned adblock off and now I see it) - something to look into.

        1. 1

          will take a look with adblock enabled and see if I can reproduce it, thanks

  7. 1

    Hello, Your landing page looks incredible!

    And Hi everyone, you may like this too! As we all know online education is evolving and people seek learning options from their homes. So, many entrepreneurs are launching their udemy-like platforms. For everyone who wants to launch their udemy-like website, it is easy as ABC with the udemy clone scripts. Checkout, the top-notch ready-to-launch udemy clone script , ExpertPlus LMS by BSEtec. The script is carefully curated with all the core features to meet all your LMS needs by a team of high-tech engineers with decades of experience.

    For more details and a free demo, click here Udemy Clone

  8. 1

    Congratulations on the idea. I love the clear and compelling headline, although I wanted to understand the app’s performance so far, but couldn’t really locate a case study.

    What you might want to go for are testimonials videos or customer success story videos that will provide social proof of your skill, establish your credibility and authority and will additionally raise awareness about your brand.

    At Camily, we work with fast growing companies such as UiPath, Asana, and Avalara, and to create 10x more video content at a fraction of the cost, while enjoying a 2.4x increase in traffic and 80% conversion rate improvement by using our video collection & embedding platform. Check out our website www.camily.io and feel free to reach out with any questions.

    1. 1

      Thanks,
      I would love to add testimonials but this is currently still in development. I have just started recording some small gif's for the main page.

  9. 1

    Great job John! I made a video for you showing you how you can improve your Landing page copy

    1. 1

      Awesome, thanks for the video feedback you have really given me lots to think about. I'm really using this project as a big learning opportunity more than anything so massively appreciate the guidance from yourself and others.

  10. 1

    I like it. It seems to hit all the right points. Well done.

    1. 2

      Thanks, I think it has improved vastly over the last couple of days since posting the original one.

  11. 1

    Hello Greenchapel_John

    Your page is excellent, but I think it needs some more work on the marketing site. Take a look at this article: https://learninbound.com/blog/8-essential-components-of-a-successful-landing-page/ to check on the components you need to add in order to convert more and attract more people to your offer.

    1. 1

      Thanks, I will have a read through the article you shared

  12. 1

    Hello, Thanks for this post.

    May all of you like this too. I think this is worth reading.

    Stay in Elearning Field Long-term! The Best Udemy Clone Script is A Key for You!

    Starting your own E-learning application is now easy. Be A Long-term Player With the Best Udemy clone script from trioangle Let's ensure more engagement.

    Gain More Learners With Smoothy Options in Udemy Clone

    https://www.trioangle.com/udemy-clone/
    E-mail: sales@trioangle.com

  13. 1

    Hey,

    1st of all I would like to praise your efforts that you are at least giving yourself a try to build https://installgeeks.com/install-facebook-messenger-bit/ a landing page. and then best of luck to your future working mate.

    1. 1

      Thanks, I'm using this one is very much a learning process :)

  14. 1

    The design appears fresh to me and easy to read. It's strange to have only one choice on the header of a website, in this case "Features". Further down, you have some misspellings, i.e. in the newsletter signup section. Here are some corrections--> "Subscribe to our newsletter to get more updates". For the line below the input field, "We will keep you up-to-date...". I would also recommend only offering to update on the single product ezConsole vs. other developments too which is too much relative to what people probably want.

    1. 1

      Thanks, I have fixed those bits and the header looks better without the single menu choice

  15. 1

    My initial impression:

    • The page title only says "ezConsole"
    • Too much text
    • The design is confusing. Why do I see "features" as the only menu option? And why below that it says "In Development?" Do you mean beta by that?
    • The header is way too big
    • The call to action is not consistent. It appears to be "app features" but then it's also "learn more"

    Since this is your first landing page, you may benefit from copying the structure of a similar website, and making changes according to that. That way you are sure to have a standard website.

    1. 1

      Hey, thanks for the feedback
      It says In Development at the moment just to point out I'm really in probably the pre-Alpha stage and trying to work out what really goes into a successful landing page.
      With the menu's, I will add some more menu Items as I do have 2 other pages (signup and contact) that should make it look not quite so wired

      1. 1

        Why don't you add that to the logo?
        In small fonts, you can add "beta" or "alpha," Like Gmail did for years
        https://www.telegraph.co.uk/multimedia/archive/01439/gmail_1439577c.jpg

        1. 1

          I like that, thanks.

  16. 1

    Hi! I don't have much feedback regarding your design, but when opening the console, I see that you've deployed a development build to production. In development mode, I can inspect your entire source code. This is just one example of the difference.

    You can create different environment files and tell Angular which one to use during a production build or development build in the angular.json file 😃

    1. 1

      Ahh, good spot, hadn't pulled over the correct scripts for package.json it just had ng build.
      I normally use with "build": "ng build --prod --aot --output-hashing=all --subresource-integrity",
      Not that if anyone wanted the code I would mind, it's only a landing page.

      1. 2

        Awesome! Just wanted to make sure 😃

  17. 1

    I'm getting a weird black loading screen before the page shows. Other than that, it looks like a landing page. I don't understand the product, so I'm probably not your target audience.

    1. 1

      Ah ok yes, it's an Angular preloader for slow connections so they can see it is loading but I can see when you are on a fast network it looks odd. I'll try setting the background of the preloader to be a light colour ( same as the main site )

  18. 1

    If i can be candid, it doesn't look great.

    There are free templates out there you can use as a base.

    1. 1

      Thanks, that's why I'm trying to get feedback as I know others wouldn't necessarily like what I do.

      1. 1

        It's great you asked for feedback. Once redone let me know and I can review it again.

        1. 1

          Hey,
          If you can take another look I worked on this, this morning, using an old template I had.
          https://ezconsole.dev/

          1. 1

            That is better.

            In terms of content I didn't have a clue what you did until right at the bottom.

            Maybe add something like https://versoly.com/ type effect on the header or below the header include a bunch of names like "DynamoDB Table Management"

            I would also add

            • Pricing page with FAQ
            • About page explaining who you are and why the product exists
            1. 1

              Thanks,
              I also like the nice big screenshot on versoly at the top.
              I don't think I am ready for a pricing page yet but could add an about page for sure.