← Previous11 / 13Next →

Vowel Product Video

VowelVideo conferencing tool that makes meetings better.

Design with AI

Create a new design inspired by Vowel Product Video, with your own content.

1Content

2Fidelity to the reference

Keeps its visual language, rearranges freely around your content.

3Your brand Optional

Use the reference style

Brand nameColorsFontsGuidelines

4Output

Prompt 933 words

# Design from Reference: Vowel Product Video

Create an original, high-fidelity visual design inspired by the reference. Prioritize composition, typography, colors, spacing, and component styling over technical implementation.

## Reference

- **Product:** Vowel
- **Category:** Product Video
- **Screenshot:** attached to this message (also available at https://media.saasframe.io/o/340714157022e763197f.webp)

Analyze the attached screenshot first. If no image is attached, open the screenshot link; if neither is accessible, ask for it rather than guessing.

## Visual Design Context

### Overall aesthetic

- **Style:** Video-meeting product preview with a stark black stage, live participant imagery and a white transcript rail. Purple gives recording and playback a recognizable accent.
- **Scale:** The image is 914 × 584 screenshot pixels. All dimensions below describe this image; CSS scale is unverified.

### Page composition

- **Stage:** The black meeting region occupies roughly 670px, or 73% of the width, with a 244px transcript rail on the right.
- **Participants:** Two approximately 315 × 177px video tiles form the upper row; a similarly sized third tile is centered below. Broad black gaps surround the arrangement.
- **Controls:** Small meeting tools run along the stage's top edge, three circular call controls are centered near its bottom, and a large white play control overlays the central tile junction.

### Information hierarchy

- **Primary focus:** Participant faces dominate, followed by the large centered playback affordance. The recording pill is visible at the upper left.
- **Transcript:** Notes and Transcript tabs sit above a vertically stacked conversation with bold speaker names and compact paragraph text. One passage has a pale lavender highlight and floating reaction/action tools.
- **Secondary actions:** Share Screen, Speaker View and an overflow icon remain small at the top; reaction emoji form a separate bottom row in the transcript rail.

### Typography

- **Family:** Compact sans-serif UI lettering; exact font identity is unverified.
- **Roles:** Transcript copy is approximately 9–10px with 14px leading at screenshot scale, speaker names bold. Top tools are around 7–9px; the recording label is around 10px.
- **Density:** Transcript paragraphs use short gaps and a narrow measure, contrasting with the image-led meeting stage.

### Colors & surfaces

- **Sampled palette:** ICC-aware sRGB samples include black #000000, white #FFFFFF and lavender #F2EFFE. Other frequent image tones include #DCE5EA and #DBE4E9 from imagery.
- **Accent treatment:** Purple visually marks recording and the play triangle; warm orange-red marks the hang-up control. The transcript selection uses the sampled pale lavender.
- **Surface separation:** A sharp black-to-white boundary divides video from text; rounded outer corners soften the whole preview.

### Components

- **Playback overlay:** Approximately 100px white circle centered around x458/y293 with a purple triangular play glyph.
- **Call actions:** Two small dark circles flank a larger orange-red hang-up circle, with microphone and camera icons in white.
- **Recording status:** A small purple pill contains an outlined circular indicator and Recording label, positioned beside the minimal product mark.
- **Transcript tools:** A compact rounded emoji strip floats above the selected passage; a smaller icon strip follows beneath it. No expanded settings panel is visible.

### Visual rhythm

- **Geometry:** Participant tiles repeat one landscape ratio, with about 10–12px horizontal and vertical gutters.
- **Contrast:** Large quiet black zones counterbalance the narrow, densely written white transcript. Bottom controls align to each region independently.

### Responsive

- **Recommended adaptation:** Only this desktop preview is observed. On narrow screens, place transcript content in a toggled drawer or below the stage while preserving usable video and playback targets.
- **Legibility:** Do not reproduce the small screenshot text size as a mobile specification; enlarge transcript text and touch controls.

### Adaptation guidance

- **Preserve:** Keep the black video canvas, simple tile grid, separate white transcript, purple playback accent and unmistakable hang-up action.
- **Replace:** Use appropriate participant imagery and real transcript content; preserve visible speaker hierarchy and selected-passage feedback without implying unseen interaction states.

## Content

**Instructions:**

Generate realistic example content that fits the selected design reference.

Create appropriate headlines, descriptions, labels, buttons, and supporting copy based on the type of interface being designed.

If a product or business description is provided, use it to guide the content.

Otherwise, invent a plausible fictional SaaS product appropriate for the reference.

Keep the content concise, coherent, and visually balanced.

Do not present fictional statistics, customer names, or testimonials as verified facts.

## Design Direction

**Instructions:**

Use the reference screenshot as the main source of visual inspiration rather than a strict layout template.

Preserve its most distinctive design characteristics, such as typography, visual rhythm, color relationships, component treatments, and overall aesthetic.

Feel free to modify section arrangements, proportions, spacing, and individual components to better suit my content.

Introduce original design decisions where they improve usability, composition, or brand consistency.

The result should clearly reflect the reference's visual language without looking like a direct reproduction.

Follow the visual identity of the reference design.

Use its typography, color palette, component styling, and overall aesthetic as the primary design direction.

Do not introduce an unrelated visual identity.

## Output

**Instructions:**

Generate a high-fidelity visual mockup of the requested interface.

Present the design as a polished, realistic website or product UI screenshot.

Prioritize visual composition, typography, spacing, colors, alignment, and component details.

Use the available image-generation or visual-design capabilities.

Do not replace the mockup with source code, a written design specification, or a textual description.

If direct visual generation is unavailable, clearly explain the limitation.

## Constraints

- Use the actual screenshot as the primary visual reference.
- Preserve essential messaging and factual accuracy.
- Prioritize visual quality and consistency.
- Do not invent unsupported product claims.
- Adapt structure and copy length for visual balance.

Reference imageAttach it to your message: assistants can’t open image links.

Build it in

Opening a tool copies the screenshot so you can paste it with your prompt.