The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Related posts
A closer look at Relay’s landing page.
My first question was: if someone lands here with no context, will they know what Relay does before they scroll?From there, I thought about what they’d need to see before taking the next step.
Clean design!
Not every new feature needs its own screen.
It's something worth thinking about when a digital product starts growing.
A new feature gets introduced, so a new page is created.
Then another feature arrives. Another page. Another menu item.
Eventually, the navigation starts reflecting everything the product has accumulated rather than how people actually use it.
And that's where things can become unnecessarily complicated.
When you're designing or improving an existing product, adding functionality isn't just about finding space for another interface.
It's about understanding how that functionality fits into the workflows people already have.
Imagine an invoicing platform introducing automated payment reminders.
You could create an entirely separate section for managing them.
Or you could integrate that functionality directly into the invoice workflow, where users already have the relevant context.
Both approaches can make sense.
If the feature involves complex configurations, reporting, or needs to be managed independently, a dedicated section might be justified.
But if it's something people naturally need while completing another task, moving them to a separate screen could introduce unnecessary steps.
I think this is particularly important with established products.
Every new feature affects more than the area where it appears.
It can change navigation, information hierarchy, existing user habits, and the overall complexity of the experience.
And the more a product grows, the more important those decisions become.
Sometimes introducing a new capability means creating an entirely new experience.
Other times, the stronger solution is making that capability feel like it has always belonged there.
Most landing pages I'm asked to fix have the same problem: they talk about the business before the customer.
The structure I start with for a Framer landing page:
1. Headline: the result your customer wants, in their words
2. Proof right under it: logos, a review or a number
3. The problem you solve, and who it's for
4. How it works, in 3 steps
5. One clear call to action, repeated at the end
If a section doesn't help someone decide, it can probably go.
Launching something soon? Send me a message and I'll sketch the page structure with you.
