FLUX UI mockup prompts: app screens and game UI via one API call
Describe layout, sections and visual style in the prompt, pick a portrait or landscape aspect_ratio, and use n to get several concepts in one Sume call.

Write the prompt as a layout brief: the screen type, the sections in order, and the visual style. BFL's guide says FLUX can generate website layouts, app interfaces and game UI mockups from descriptive prompts about structure and visual style. On Sume you send that prompt to POST /v1/images with a FLUX.2 id, an aspect_ratio that fits the screen, and n for variants.
BFL's guidance is from its UI Mockups page; request fields from Sume's Image API docs, read 2026-10-01.
What should a UI mockup prompt contain?
BFL's wording is to describe the layout structure, content sections and visual style. In practice: the device or window, the top-to-bottom order of regions, the text each region shows, and a style line such as "flat, light theme, rounded cards". Treat the result as a design concept, not production art.
Which request fields matter?
| Field | Use for a mockup |
|---|---|
model | A catalog id such as black-forest-labs/flux.2-pro |
aspect_ratio | 9:16 for a phone screen, 16:9 for a desktop or game screen |
n | Number of images, 1–10, to compare layouts |
image_size | Custom pixels on models that accept them, including Flux |
What does the call look like?
const res = await fetch("https://api.sume.com/v1/images", {
method: "POST",
headers: {
Authorization: "Bearer " + process.env.SUME_API_KEY,
"Content-Type": "application/json",
},
body: JSON.stringify({
model: "black-forest-labs/flux.2-pro",
prompt:
"Mobile app home screen for a habit tracker: header with date, three habit cards with progress rings, bottom tab bar. Flat, light theme.",
aspect_ratio: "9:16",
n: 4,
}),
});
console.log(res.status, await res.json());What if a generation outlasts the wait?
Sume caps a blocking wait at 30 seconds; slower generations return a job envelope with 202 and you read the images from the job result. For ratio rules see image API aspect ratios and custom sizes.
Sources
Related posts
More in Use cases
- FLUX Virtual Try-On v2: 4 MP inputs and a Sume reference edit
BFL's vto-v2 keeps inputs up to 4 MP as-is. Sume has no try-on endpoint in these docs; a garment swap is a reference edit with public HTTPS images.
- AI frame interpolation API: 24 to 60 fps on Sume
Sume has no AI interpolation model. Timeline repeats or drops frames to reach 60 fps, video filter allows an ffmpeg framerate filter, and setpts is refused.
- FTC: actors, dramatizations and scripted AI avatar ads
The FTC Q&A says actors in an obviously fictional dramatization are not giving testimonials, yet could still be deceptive. What that means for avatar ads.
- Is #ad enough in a video? What the FTC Q&A says
The FTC says #Ad may work at the start of a text post but may be too easy to miss in a video. Text in a video must stand out. Sume captions burn it in.
Written by Sume