Case study

AI-Powered App Threadline for Higgsfield Supercomputer

A visual launch generator for brands — one mockup in, a full brand presence out.

Outcome: Built end-to-end in 3 days · live app · $100K Higgsfield App Contest entry

  • Type: Challenge entry
  • Client: Higgsfield AI
  • Role: UI Designer, Vibe Coder
  • Year: 2026
  • Tools: Claude Code, Cloudflare D1, Higgsfield Supercomputer, Figma Make
  • Tags: Product Design, Vibe Coding, Generative AI, Contest

View the live project

The case in brief

Context
An entry for the $100K Higgsfield App Contest, built on the Higgsfield platform for small clothing brands and print-on-demand sellers.
Problem
Small brands rarely have studio resources — just a product mockup and a deadline. Styled photos, video and launch copy normally take weeks.
Scope
Product design and build of a working app: upload a mockup, set the brand style, get a full launch pack (product photos, lookbook video, UGC clip, copy), plus inline photo fixes, persistent history and regeneration.
Role
UI Designer, Vibe Coder
Constraints
Three days, July 20–22, 2026. It had to feel native to Higgsfield — its Quanta design system and brief-first flow. Which generation engines are available depends on the user's plan.
Key decisions
  1. Shaped the app to feel native to the Higgsfield ecosystem instead of inventing a new interface, while keeping its own product character.
  2. Every visual prompt is deterministic composition from a typed vocabulary; an LLM writes only the copy pack.
  3. Same Model mode chains the finished photo into the video jobs, for real model consistency rather than a text hint.
  4. A silent engine fallback chain, so no raw API error ever reaches the user.
Outcome
Built end-to-end in 3 days · live app · $100K Higgsfield App Contest entry
Reflection
A working app in three days. The lesson for next time: the platform's shared components carry desktop-first defaults — hover-only actions, fixed grids, side-by-side panels — worth checking on mobile before trusting them, even when a responsive option already exists.

Threadline — An AI Launch Studio for Brands

Turn one product mockup into styled photos, lookbook & UGC videos, and ready-to-post captions in minutes.

  • 3 — Timeline — Days built end-to-end, July 20–22, 2026
  • $100K — Contest — Higgsfield App Contest entry
  • 47 — Views — 47 views, 12 likes on Contra

Threadline App

The Idea

Small clothing brands and print-on-demand sellers rarely have studio resources — just a product mockup and a deadline. Threadline accepts a single mockup upload and generates a complete launch package: styled product photography, a lookbook video, UGC-style footage, and social captions, in minutes instead of weeks.

Threadline App

Higgsfield defines not only the visual style of the interface, but also the interaction logic itself: a brief-first workflow, a step-by-step flow, model selection based on the task, and built-in creative workflows. So the goal was not to invent a brand-new interface, but to shape Threadline so it felt native to the Higgsfield ecosystem while still having its own distinct product character.

Product flow

  1. Upload Your Mockup — add a product mockup and basic product details.
  2. Set the Brand Style — choose mood, scene, audience, talent mode, copy tone, and generation engines.
  3. Get the Full Launch Pack — receive product photos, a lookbook video, a UGC clip, and launch copy ready to deploy.

Input

A PNG/JPG of the print or flat-lay — the only thing the user has to provide.

Control

Category, mood, scene, audience, copy tone — these drive the entire pack.

Output

Photos, lookbook video, UGC clip, copy pack — ready to post.

Implemented Features

  • Product Photo Pack — 4 styled e-commerce shots per generation, one shoot's worth of poses, picking from Nano Banana 2 / GPT Image 2 / Soul 2.0.
  • Lookbook Video Pack — cinematic, slow-motion runway-style footage, with an engine choice between Seedance 2.0 / Kling 3.0 / Veo 3.1 Lite.
  • UGC Video Pack — a handheld, candid, phone-camera-style clip, deliberately scripted to open on the opposite kind of shot from the Lookbook.
  • Launch Copy Pack — product description, ready-to-post captions, hashtags, and content ideas via real LLM calls — the sole place an LLM writes freely.
  • Fix This Photo — an inline editor for typed adjustments ("remove the necklace, make the background lighter"), regenerating a specific shot using itself as reference.
  • Regenerate from History — reopen past generations, view stored prompts, pick a different engine, and regenerate chained from the original input image, not the prior output.
  • Persistent History — every generated photo and video saved chronologically with type badges, merged rather than grouped photos-then-videos.
  • Saved Copy Packs — every generated copy pack saved per-launch and browsable from History.

Input

Upload your mockup — add one product mockup and basic product details.

Output

4 styled e-commerce shots per generation, one shoot's worth of poses, picking from Nano Banana 2 / GPT Image 2 / Soul 2.0 as the rendering engine.

UGC Video — handheld, candid, phone-camera-style clip — deliberately scripted to open on the opposite kind of shot from the Lookbook (tight and already-rolling vs. wide and already-moving), so the two videos read as two different moments of the same shoot instead of one template wearing two moods.

Cinematic, slow-motion runway-style clip, engine choice between Seedance 2.0 / Kling 3.0 / Veo 3.1 Lite.

Product description, ready-to-post captions, hashtags, and content ideas, generated through a real LLM call (the only place in the whole app where an LLM writes freely — every visual prompt is deterministic string composition, not LLM-authored).

An inline editor on any generated photo: type what to change ("remove the necklace, make the background lighter"), pick a model, and it regenerates that specific shot using itself as the reference — without rebuilding the whole pack.

Every photo and video ever generated is saved and browsable, chronologically merged (not "all photos, then all videos"), with type badges so photo vs. video is obvious at a glance.

Reopen any past generation, see its real stored prompt, pick a (possibly different) engine, and regenerate — chained from the original input image, not the prior output (more on why that distinction mattered below).

Engineering Deep Dive

Every photo and video prompt is built from a typed vocabulary — category × mood × scene × audience × talent mode — via pure string-composition functions. Never an LLM improvising the brief.

— The Prompt Engine — Deterministic Composition

Same Model mode changes the actual sequence of API calls: the Photo Pack submits and completes first from the original mockup, and that finished photo then becomes the image reference for the Lookbook and UGC video jobs — real model consistency, not a text hint asking the model to "keep the same person." Mixed Cast skips this entirely: all three packs generate in parallel straight from the mockup.

The app never surfaces a raw API error. Every pack carries a silent fallback chain: if the chosen engine isn't available on the user's plan, Threadline automatically retries the next one in the fallback order, with zero raw API errors ever reaching the user. Any other failure (out of credits, gateway down, unknown error) breaks the chain immediately and shows plain, understandable text instead — no status codes, no provider jargon.

The product description, captions, hashtags, and content ideas are the one part of the app generated by a real LLM call rather than deterministic composition — required to return one strict JSON object, no markdown fences, no commentary, and explicitly instructed to avoid AI-cliché language and write like a real founder talking to real customers.

Technical Stack

  • TanStack Start (SSR) on Cloudflare Workers
  • @higgsfield/fnf SDK for generation jobs
  • Cloudflare D1 for launch persistence
  • Quanta — Higgsfield's internal design system
  • Nano Banana Pro / GPT Image 2 / Soul 2.0 for photos
  • Seedance 2.0 / Kling 3 / Veo for video

Mobile Considerations & Design System Learnings

  • Hover-only actions — the CardActions component shipped hover-gated only, making actions unreachable on touch. Fixed by making the action rail always-visible.
  • Card flex-direction lock — the base Card component forces column layout, silently collapsing custom row layouts. Fixed with one explicit flex-row override.
  • Fixed grid responsiveness — VirtualGrid supports a responsive minColWidth option, but a fixed cols={5} shipped under time pressure. Switched to minColWidth for a proper 375px phone display.
  • Side-by-side modal stack — the generation-detail lightbox pinned its info panel at 366px with no mobile fallback. Fixed by stacking the panel below the media under the md breakpoint, in a single scroll container.

The platform's shared components carry desktop-first defaults worth checking before trusting them on mobile — and even when the responsive option already exists, it's easy to reach for the fixed one first.

Try Threadline for yourself

Launch app

All projects · Start a project