← Previous8 / 15Next →

VideoAsk User Onboarding

VideoAskGet personal with your audience

Design with AI

Create a new design inspired by VideoAsk User Onboarding, 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 1,111 words

# Design from Reference: VideoAsk User Onboarding

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

## Reference

- **Product:** VideoAsk
- **Category:** User Onboarding
- **Screenshot:** attached to this message (also available at https://media.saasframe.io/o/e8f7ddd6716eb52987fe.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

- **Character:** A split creator-onboarding screen with stacked white settings cards on light gray and a large live-style preview on white. Purple configuration accents pair with a green creation action.
- **Image basis:** The 1440 × 821 source was inspected at approximately 1400 × 798. Measurements below are inspection-pixel estimates; CSS scale and font identity are unverified.

### Page composition

- **Configuration pane:** A roughly 536 px wide gray left region contains a two-line introduction, five stacked control cards and bottom navigation.
- **Preview pane:** The right side centers a browser-like preview beneath a small gray scale caption, followed by desktop/mobile device icons.
- **Preview content:** A video/image panel occupies the left half of the miniature browser; the right half offers three response-format buttons.
- **Dismissal:** A purple cross and tiny ESC label occupy the upper-right corner of the page.

### Information hierarchy

- **Task:** A short regular line and bold follow-up announce the final setup stage.
- **Settings:** A name input leads, followed by contact collection, language, branding and colors.
- **Primary action:** The broad green Create videoask button anchors the configuration pane beside a small gray back action.
- **Observed state:** The name input shows a caret and purple underline; contact collection is off. Desktop preview is emphasized while the phone icon is muted. No validation or completed state is visible.

### Typography

- **Introduction:** Approximately 21 px sans-serif, with the second line semibold.
- **Controls:** Name placeholder is around 20 px; settings labels and values are approximately 13–14 px, with bold selected values.
- **Primary action:** Approximately 20 px semibold white text.
- **Preview:** The scale caption is around 16 px gray. Miniature preview title and response labels are illustrative, smaller text. Typeface identity is unverified.

### Colors & surfaces

- **Measured base:** White #FFFFFF forms cards and preview; gray #F0F0F0 forms the left pane.
- **Measured accents:** Green #6FDA83 fills the creation action; purple #8250FD appears in swatches, help icons and preview response controls.
- **Measured neutrals:** #E0E0E0 and nearby #EFEFEF, #EDEDED and #E9E9E9 occur among switches, browser chrome and shadows.
- **Artwork:** The video still supplies photographic darks and skin tones. These belong to content rather than the interface palette.

### Components

- **Name card:** Approximately 413 × 78 px with around 13 px corners, soft shadow and an underlined input inset about 16 px.
- **Settings rows:** White rounded cards range from roughly 55–87 px high, with consistent width and subtle shadows.
- **Switch/help:** A compact gray off switch aligns right in the contact row; small filled purple question circles accompany configuration options.
- **Selectors:** Language and branding rows use bold current values with down chevrons, plus muted secondary actions at the right.
- **Color controls:** Two approximately 43 px square rounded swatches sit right aligned in the Colors card.
- **Footer actions:** A roughly 48 × 55 px gray back button precedes a roughly 358 × 55 px green creation action.
- **Preview frame:** Approximately 530 × 415 px with rounded corners, light browser chrome and a subtle shadow. Three purple square response buttons sit in its white right half.
- **Device controls:** A dark desktop outline and muted phone outline sit below. No opened selector or hover state is shown.

### Visual rhythm

- **Stacking:** Consistent roughly 14–16 px gaps separate settings cards; labels and right-side utilities align across rows.
- **Balance:** A dense configuration stack contrasts with broad preview whitespace.
- **Anchoring:** The large creation button sits below a substantial gap, marking the end of the setup sequence.
- **Geometry:** Repeated soft corners and faint shadows unify form cards and preview, while colored swatches provide compact accents.

### Responsive

- **Evidence limit:** Only the wide split layout is observed.
- **Recommended flow:** Stack configuration before preview on narrow screens, retaining a clear creation action after settings.
- **Recommended controls:** Keep switch/help hit areas usable and allow row utilities to wrap without obscuring selected values.
- **Recommended preview:** Scale proportionally or provide a deliberate mobile preview rather than shrinking all content indefinitely.
- **Recommended dismissal:** Maintain a clearly labeled close action and keyboard support.

### Adaptation guidance

- **Preserve:** Keep the explicit final-step hierarchy, grouped settings, prominent creation action and immediate preview.
- **Build:** Reuse setting-row, toggle, color-swatch and preview-frame components.
- **State design:** Define required-name validation, selector menus, preview device switching and creation progress separately.
- **Validate:** Confirm focus visibility, green/white action contrast, keyboard operation and narrow-screen preview behavior.

## 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.