1Dapp Constructor

A memecoin lives or dies in its first day. The token is the easy part: a launchpad mints it in minutes. What the team cannot produce that fast is the thing every holder, aggregator and listing reviewer checks first, a site that looks like somebody is home.

Teams solve this in three bad ways. They buy a template and hand edit HTML. They open Framer or Webflow and lose two days learning a canvas. Or they ship nothing and let a Telegram channel be the whole brand.

So the design problem was never "make a website builder". It was how few decisions can produce a credible site, and how do you stop the user from wrecking it afterwards.

Four barriers stand between a team with a contract and a site anyone would trust. Each one got a direct design answer, and each answer cost something.

This was desk research. No user interviews, no usability sessions, no analytics. What I had was the market itself: shipping launchpads, competing builders, the documentation memecoin teams actually follow, and a wall of reference UI.

So I treated everything below as a model to be argued with, not a finding. The jobs and the journey are reconstructions from public behaviour. Saying that up front is not a weakness, it sets you up to judge the reasoning, which is the part that was mine.

A constrained product is a stack of trade offs, and a case that lists only the wins is not worth reading. Every decision below bought something and gave something up.

The one worth defending hardest is the last: desktop only, with a designed mobile dead end. Rather than a broken responsive editor, mobile gets an honest wall with a reason, a tutorial link and a way back. What mobile does keep is read only management.

Every step has the same shape: choices on the left, live laptop and phone preview on the right, Back and Next pinned to the bottom. The progress bar names all five steps from step one, so the user always knows how much is left.

Step one also carries the paid logo service, priced inline. The upsell appears at the exact moment the user discovers they do not have a logo, which is the only moment it is useful rather than annoying.

Three columns, no floating panels. Left is the navigator: pages, the section tree, and the media library. Centre is the canvas at real width with a persistent Add Section affordance, four device toggles, and Publish as the only accent coloured button in the app.

Right is the inspector, and it always has the same two tabs. Components exposes what the section contains as toggles and slots. Style exposes paddings, full width, sticky behaviour, background and shadow. Content edits never touch layout, which is the whole point.

Header, hero, about token, tokenomics, the contract block, roadmap, how to buy, partners, FAQ, join community, footer. Each one carries the vocabulary this market checks for, and each has its own inspector panel.

Nested components drill down rather than crowd the panel. Selecting the tokenomics chart pushes a Chart panel with per slice value, colour and an add slice action, with a way back to the parent.

Publishing is a single modal: one fixed price per website, three lines of what that includes, chain select, pay and publish. No monthly tiers, no feature grid, no trial. For a buyer whose product may not exist in a week, a subscription is the wrong ask.

The number was set against what the alternative costs, not against other builders. A freelance memecoin site ran several hundred dollars and several days, so pricing one publish below that, with the site still editable afterwards, makes the comparison easy to do in the buyer’s head at the paywall.

Unpaid projects stay usable and carry a banner instead of a lockout. Domains get the full three state flow: availability check, pending approval with the exact CNAME name and target, then approved.

Every number here was counted from the Figma file, not estimated. They are the only numbers in this case, and they carry the weight that business metrics would carry if I had them.