---
title: "Why You Need to Delete the Hero Section?"
url: https://daily.dev/posts/why-you-need-to-delete-the-hero-section--6hoand53i
source_url: https://daily.dev/posts/why-you-need-to-delete-the-hero-section--6hoand53i
type: freeform
source: "Yeden Sherpa"
author: "Yeden Sherpa"
published: 2026-02-02T12:52:35.780Z
updated: 2026-02-02T12:52:52.006Z
tags: ["ux", "ui-design"]
reading_time: 2
upvotes: 2
comments: 1
language: en
---

> ## Documentation Index
> Fetch the complete documentation index at: https://daily.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Why You Need to Delete the Hero Section?

**[Yeden Sherpa](https://daily.dev/sources/auozg8gqe2bjo1ap2ggzm)** · [@yedensherpa](https://daily.dev/yedensherpa) · 2 min read · 2 upvotes · 1 comments

## Summary

A product designer shares how removing the traditional hero section with a CTA button and replacing it with the actual typing interface dramatically improved user engagement. Instead of asking users to read, decide, and click before experiencing the product, the new design lets visitors immediately interact with the typing tool, reducing time to first meaningful interaction from multiple steps to instant hands-on experience. The key insight: if your product's value can be demonstrated in under 5 seconds, show it immediately rather than hiding it behind buttons.

## Content

When I first launched nativetype.com, the hero section followed a familiar formula:

1. Headline
2. Short Description
3. Big, Confident "Get Started" button

Textbook stuff.

Button was there waiting for people to click.

Let me tell you what nativetype is. It is a tool for typing in native scripts (Nepali, Hindi, Tibetan, Urdu, Newari, Limbu etc).

Typing is the core interaction.

Yet the original hero section followed usual SaaS pattern which I've mentioned at the top.
1. Read
2. Decide
3. Click
4. Then finally interact

People were landing on the site, scrolling a bit, reading for a few seconds, and leaving; without ever typing a single character. I think it asked users to commit before they understood the value.

That's when it hit me:
Typing is a product. Why was I hiding it behind a button?

The Change:

I removed the primary CTA entirely and replaced the hero section with the actual typing interface:
Language selector
Input field
Live keyboard
Immediate feedback on keystroke

Most importantly, users understood Nativetype without reading a single paragraph.

Why this worked?

This change reduced the time of first meaningful interaction.
From user's point of view:
- Does this support my language? -> type character
- Does the layout feel correct? -> type a word
- Is this usable on my device? -> instantly clear

From a system perspective:
- A functional demo
- A capability check
- A confidence builder

The biggest takeaway is if your product's value can be demonstrated in under 5 seconds, don't hide it behind a CTA.

For nativetype, removing a button improved clarity, reduced friction and UI aligned with actual system behavior.

![Screenshot 2026-02-01 at 16.20.41](https://media.daily.dev/image/upload/s--xKZfAHVv--/f_auto/v1770036696/ugc/content_80e76366-764b-443e-91a3-a145301e80ee?_a=BAMAMiiu0)

## Community discussion

Top comments from developers on daily.dev.

**@tanchhohangbegha** · 0 upvotes

> niceee gurujiii👌

## Similar posts on daily.dev

- [Hero Images are Dead. These Solutions are Replacing Them.](https://daily.dev/posts/hero-images-are-dead-these-solutions-are-replacing-them--xydprja85) · UX Planet · 194 upvotes · 5 comments
- [The 3-Second Rule: Why Your MVP Landing Page Isn’t Converting \(And How to Fix It\)](https://daily.dev/posts/the-3-second-rule-why-your-mvp-landing-page-isn-t-converting-and-how-to-fix-it--amkuxmubm) · Medium · 0 upvotes · 0 comments

---

Tags: [#ux](https://daily.dev/tags/ux), [#ui-design](https://daily.dev/tags/ui-design)

[View this post on daily.dev](https://daily.dev/posts/why-you-need-to-delete-the-hero-section--6hoand53i)