1
8 Comments

CookUp Recipe Manager Landing Page

Hey IH! I'm getting closer to launching CookUp on PH - have just recently got the android version up and running. Would love a critique of the landing page before I do so to make sure I've got it to a good enough point where driving traffic won't be a waste.

Please do take a loo

  1. 2

    Hey Greg,

    I have some thoughts on your copy and design.

    Copy:
    I like that you generally have a conversational tone. The benefit is unclear to me though.

    Headline:
    "Choosing recipes should be simple." - This is a pretty vague idea. Choosing them from where? Simple compared to what?

    What made you build this?

    Did you find yourself, or somebody you know, constantly wanting to save recipes online and having to bookmark the page, come back and copy/paste the info to some other storage?

    Looking at the product, it feels a little like Pinterest for recipes.

    Tap into how and why somebody might want to use this. Telling them that choosing recipes should be simple is passive. Make it active.

    Something like - "Find a great recipe online? Add it to your collection with CookUp".

    Something like that lets people know immediately what the app is about and why they want to install it.

    Then your subhead could be something like - "Make mealtime awesome with your own curated collection of delicious recipes." Something to tap into why you want to collect recipes in the first place.

    Small note - "Don't you think? we do" <- Capitalize "We".

    Feature Bullets:
    "Save from browser" sounds a little robotic. It also doesn't speak to the customer about a benefit. Pull in that conversational tone and draw out the experience your user might have using the app.

    Something like - "Found a new recipe on your favorite site?" In the supporting content block, continue that conversation and let them know they can save it for later.

    I recommend not using words like "parse" in the description. That's tech jargon that people aren't interested in. That's how you might explain it to a tech investor or somebody on your team. Customers only need to know that if they see a recipe on a site, they can save it for later use.

    Make it exciting. Get into their head when they see the recipe. People save recipes because they want to try something new, need ideas for dinner that night or possibly an event in the future. Write copy that talks to them about that.

    Small note - You tell them to "save" and "share" in different parts of the copy. Stick to one.

    "Simplify Meal Prep" is also a little dry. It's a benefit but I wonder if it's something people actively seek out. Why do we want to simplify meal prep? Is it because cooking is overwhelming? Is it because we ultimately want to nail a recipe so we can feel like Gordon Ramsey? Pull out some emotion here. Make it interesting.

    If you were watching a cooking show host on TV and they said "Today we're going to simplify meal prep", would that be exciting? If they said, "Today, you're going to rock this recipe like a real chef", would that pique your interest a little more? Find the tone that fits you and dress it up a little.

    The "Our Recipes" link at the top is a little oddly placed. I know that you're trying to show what the app does but there's no context given to the link. The way it is now, a customer has to overcome a cognitive load. Are these recipes you saved? Are these recipes you created? Is this a recipe site itself?

    I like the idea of including the output from the app but I would move it into the landing page as a content section.

    Design:
    That segues into the design thoughts.

    When you click on the "Our Recipes" link, it takes you to a new page that is branded differently. The recipes page has a logo/icon. It doesn't say CookUp anywhere. The colors are all different, with the exception of the icon carrying the hero background from the landing page.

    Back on the landing page, your app screenshot is bleeding into the white frame of the device mockup. The battery icon hits the frame. Add some padding there to clean that up.

    Do the same in the "Save from browser" screenshot. Add some padding under the "See in CookUp" button. Let it breathe a little. Also, that's a third verb for how it works. "See", "Save", "Share". Iron out that language.

    The text color in the FAQ section is too light. There isn't enough contrast. If you were to look at this on a sub-optimal device, that's going to be hard to read.

    Same for the Contact Us section. It needs more contrast. I'd also recommend just making the inputs have a white background. No reason that those should be subdued.

    The "Send Message" button is a cardinal sin :) Your button should give them some kind of indication of what is going to happen when they click. Why should they send this message? Is it to simply provide feedback? Is it really just to ask a question? What is going to happen when they send their inquiry?

    I would change it to something more conversational at the very least. I don't imagine you would tell your friend to "Send Message" when they need to contact you.

    Make it something real. "Hit us up" (If that's how you talk), "Let us know how you feel". You get the idea.

    The app looks cool. Good luck, I hope it takes off!

    1. 1

      Wow - this is so so very useful! Amazing! I cannot thank you enough for the thorough feedback - going to get on this right away.

      1. 1

        You mind if I used this as a testimonial?

        1. 1

          Not at all, go ahead - let me know if you need anything from me

      2. 1

        Awesome. I hope it helps. Good Luck

  2. 1

    Greg I really liked the top 2 parts of the landing page, but the light blue background with grey bordering, and the white/red 'send message' box was a little rough on the eyes. Again, other than that, it looks really good! Good luck!

    1. 1

      Ah yeah that is rough to look at! I’ll get that fixed up, thanks for the feedback Matt!

Trending on Indie Hackers
Competing with Product Hunt: a month later 33 comments Why do you hate marketing? 29 comments My Top 20 Free Tools That I Use Everyday as an Indie Hacker 18 comments $15k revenues in <4 months as a solopreneur 14 comments Use Your Product 13 comments How I Launched FrontendEase 13 comments