loom

loom presents as a brand in final preparation. visitors land on a soft photographic field, read a short coming soon line, and submit a work email for early access consideration. after submit, the card swaps to a quiet request received state.

that is the whole product story on purpose. no feature grid. no pricing. no long scroll. just brand presence, one action, and enough polish that the fiction feels intentional.

visually it mixes syne for display and figtree for body. the card sits as glass over the image. spacing stays generous so the page can breathe.

i built loom as a single static page. html for structure. a small css set for the hero and card. javascript for the waitlist interaction and the success state.

the constraint was extreme focus. if a coming soon page needs a framework to feel real, something is wrong. plain front end kept the loop fast: adjust type, refresh, judge the weight of the card against the photo.

coming soon pages often look abandoned or over designed. loom aims for the middle: enough structure to feel like a real brand moment, not enough chrome to pretend there is a full product behind it.

the form note stays honest inside the fiction: a single confirmation email. the success state uses a simple check and short copy so the feedback feels calm, not celebratory spam.

loom is not live software. there is no real waitlist service, no crm, and no product launching behind the card. if you submit an email expecting access to something, you will only meet a designed demo.

that honesty matters. the page is a portfolio piece about focus and finish on a tiny surface. the company is imaginary. the craft is not.

i ended with a complete one screen marketing moment for a product that does not exist. it sharpened how i handle waitlist ux, card hierarchy, and photographic heroes. loom is a personal mock i finished enough to show, clear enough to say out loud that it is not a real launch.