· 4 min read · AI, Web development, Process
A coming-soon page built with AI, skipping the prototype

I'm a designer with little coding experience. For Prompt Wizards I built a live, interactive "Coming Soon" page with AI help and never made a Figma prototype first. Here is what I did, what I think it shows, and where I'd be careful.
What I built
The page is live. Elements animate as you scroll. That comes from GSAP (the GreenSock Animation Platform), a JavaScript animation library, and its ScrollTrigger plugin. You set a trigger point, say "when this element enters the screen", and describe the animation. ScrollTrigger ties it to the scroll position. The docs say it doesn't hijack native scrolling, which is a good sign for usability.
You can read the project page for the short version.
Why skip the prototype?
Traditionally a designer draws the page in Figma, then hands it to a developer. Things can get lost in that handoff. A scroll animation is hard to show in a static frame anyway. So I went straight to the real thing, and the real thing is what people can open.
The tools are there. Vercel's v0 turns a prompt into React code. Anthropic added Artifacts to Claude in June 2024, so code or a page design shows up next to the chat. Lovable rebranded from GPT Engineer to build apps for people without deep coding experience. Cursor's editor got an early agent in November 2024 that can pick its own context and use the terminal.
Figma moved the same way. At Config 2024 it showed Make Designs, which gives you a "first draft" from a text description. Figma pulled it in July 2024 after a weather app prompt gave results "very similar to Apple's first-party app". It came back in September as First Draft, in limited beta, with a choice of four libraries. Figma calls it a "jumping-off point", not a finished design.
What AI gives a designer
These are the benefits I see:
- Faster prototyping. Something real, quickly, without writing it all myself.
- More creativity. It's cheap to try several variations.
- Better collaboration. A working page shows my intent more clearly than a frame does.
The honest counterpoints
You may not understand what you ship. A study had people write code with and without an AI assistant. Those with the assistant wrote significantly less secure code, and were more likely to believe it was secure. It tested programming tasks with an older model, not landing pages. But the warning fits. If I can't read the code, I can't check it.
Motion has a cost for some people. MDN says large scaling or panning movement can trigger discomfort for people with vestibular disorders. The prefers-reduced-motion setting lets a page respect what the user asked their device for. WCAG 2.1 has a rule on this, 2.3.3: motion triggered by interaction can be disabled. It is level AAA, the strictest level. GSAP's docs show how to use the setting with gsap.matchMedia(), added in version 3.11. AI-generated animation code won't always include it. You have to ask.
Speed needs care. Chrome's guidance is to animate transform and opacity and avoid properties that force layout. Generated code can get this wrong, and a coming-soon page on a phone is where you'd notice.
Generic output. Figma's Apple lookalike incident and its "jumping-off point" wording both point at the same limit. These tools lean on what already exists. Original work still needs a designer's eye.
My view
This is an opinion. A prototype is for learning something cheaply. A live page is cheap now too, so for a simple page, skipping the prototype makes sense. For anything with users, accounts or data, I'd want a developer to look at the code. The designer's job moves from drawing the page to judging it: motion, contrast, speed, and whether it still works for everyone.
Sources
- Config 2024 in review (Figma, 26 June 2024) - announcement of Make Designs and its "first draft" wording
- Inside Figma: a retrospective on Make Designs (17 July 2024) - the pause after the weather app similarity
- Building a better First Draft for designers (Figma, 24 September 2024) - the rename, four libraries, limited beta
- ScrollTrigger docs (GSAP) - what the plugin does; it existed well before this date (added in GSAP 3.3.0)
- gsap.matchMedia() docs - reduced-motion pattern; added in 3.11.0
- prefers-reduced-motion (MDN) - vestibular concerns; docs page, feature long supported by browsers
- WCAG 2.1 (W3C, 5 June 2018) - success criterion 2.3.3, Animation from Interactions
- Animations guide (web.dev) - performance advice; undated docs page
- Do Users Write More Insecure Code with AI Assistants? (arXiv, Nov 2022) - study on overconfidence and insecure code
- Vercel v0 public beta (DevClass, 10 October 2023) - what v0 does
- Claude 3.5 Sonnet and Artifacts (Anthropic, 21 June 2024) - Artifacts launch
- Rebranding GPT Engineer to Lovable (Lovable, Dec 2024) - tool aimed at people without deep coding experience
- Cursor 0.43.x changelog (24 November 2024) - early agent in Composer
Comments