The hardest part of building a crypto product for beginners isn't the cryptography. It's figuring out what to put on the front door.
nimimo does a lot under the hood. Device-bound encryption. Cross-chain key derivation. Recovery cards with split storage. A layered security model where access, identity, ownership, and recovery are all independent systems. We could write pages about each of these. We almost did.
The instinct to over-explain
When you've built something technically interesting, there's a gravitational pull toward showing it all. We wanted to put code on the landing page. Walk people through how key generation works. Show the architecture diagram. Prove that the system is sound.
But then you ask: who is this for? The person who's never touched crypto doesn't care about your encryption primitives. They want to know if this thing is safe and simple. The engineer who might actually read your code isn't going to trust pseudocode on a marketing page.
A landing page has one job: make someone want to try it. It's not a whitepaper. It's not a README. If someone needs to understand your key derivation before they'll sign up, your landing page has already failed — because that understanding should come from using the product, not reading about it.
Saying less is harder than saying more
We went through multiple rounds of cutting content. Not because it was wrong, but because it was redundant. Three different sections that all communicated the same idea — 'nimimo is simple, you don't need to be an expert' — in slightly different words. Point taken after the first time. By the third, it sounds like you're trying to convince yourself.
Every section has to earn its place. If two sections make the same point, one of them goes. If a paragraph restates the heading above it, the paragraph goes. You keep cutting until what's left is the minimum someone needs to understand the product and feel confident enough to try it.
This is counterintuitive. More information feels like more trust. But in practice, a page that says too much reads like it's compensating. Confidence is short sentences. Trust is making a clear promise and stopping.
Only say what's true — and what stays true
Every claim on the landing page has to pass two tests. Is it true right now? And will it still be true in six months?
This sounds obvious, but it's easy to write aspirational copy in a trust section. It's easy to make promises that are technically true today but won't survive the next product decision. A landing page isn't a snapshot — it's a contract. If someone reads it today and comes back in three months, it should still hold.
The same goes for comparing yourself to competitors. It's tempting to list every flaw in the alternative. But if you share any of those flaws — even in a different form — the comparison undermines itself. Better to focus on what's genuinely different than to pretend you've solved everything.
The landing page is not the documentation
This was the biggest lesson. We kept trying to put architecture on the landing page because we're proud of it. But architecture belongs in blog posts, in documentation, in the product experience itself. The recovery card flow teaches you about backup by having you do it. The wallet tab teaches you about self-custody by showing you your keys. That's where understanding happens — not on a marketing page.
A security section that says 'Your keys never leave your device' in one sentence is more convincing than three paragraphs explaining exactly how. If you have to explain at length why you're trustworthy, you probably aren't.
Building with AI is not one-shot
We use AI tools to build nimimo. Some people hear that and assume the product is generated in a single prompt. Type a sentence, ship whatever comes out. That's not how this works.
nimimo is hundreds of tiny decisions. What the headline should say. Whether a section earns its place. Whether a comparison is fair. Whether a claim will age well. Whether a modal is too large on mobile. Whether the tone is confident or compensating. Each of those is a human judgment call.
AI tools write code fast. They research well. They generate first drafts in seconds. But the product lives in the corrections — the small adjustments between the first version and the one you actually ship. A tool that moves fast doesn't remove the need for taste. It just gives you more time to exercise it.
The gap between 'AI-generated' and 'AI-assisted' is the same gap between a rough draft and a finished piece. The draft is the easy part. The craft is everything after.
What stays and what moves
The landing page is lean now. A clear promise. A simple walkthrough. An honest comparison. The core identity concept. A security statement that says what it needs to and stops. And a blog for everything else.
Everything we cut is still true. It just lives somewhere better — in these posts, in the product, in the flows that teach by doing. The landing page opens the door. It doesn't need to be the entire house.