← Previous6 / 32Next →

Livestorm Session Dashboard

LivestormVideo Conferencing

Design with AI

Create a new design inspired by Livestorm Session Dashboard, 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 746 words

# Design from Reference: Livestorm Session Dashboard

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

## Reference

- **Product:** Livestorm
- **Category:** Dashboard
- **Screenshot:** attached to this message (also available at https://media.saasframe.io/v/467aa06441770e13c8bf-1600.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:** Light event-management dashboard with a dark teal icon rail, pale-gray canvas and blue/green event actions.
- **Scale:** Source 2880 × 1642px; dimensions estimate a 1440px-wide CSS viewport at 2× capture scale.

### Page composition

- **Shell:** A roughly 88px vertical rail contains Events, Calendar, Instant, People and lower app/account controls.
- **Header:** Event title sits left; registration/event-room links and upgrade/publish/add-session actions align right.
- **Content:** Sessions tabs and filter/search toolbar precede one centered session card on a mostly empty pale canvas.

### Information hierarchy

- **Current view:** Sessions is selected beside People, Email invites, Recordings and Settings.
- **Session:** A draft session card shows avatar, title, date/time and registration/team counts.
- **Timing:** A small in 4 days label appears left of the card on a faint timeline point.

### Typography

- **Family:** Neutral sans-serif; exact font identity is unverified.
- **Roles:** Estimated title 20px bold, tabs/body 16px, session title 14px semibold and counts/status 12px.
- **Contrast:** Dark slate headings contrast with muted metadata and compact uppercase Draft badge.

### Colors & surfaces

- **Sampled palette:** ICC-aware sRGB samples include #F6F7F9, white #FFFFFF, teal #0A272B/#0C262C, green #00A976, blue #0043CB and pale #E9EEF1.
- **Actions:** Green identifies Publish event, blue Add session and outlined green Upgrade now.
- **Depth:** White session card has subtle shadow and small corners; toolbar uses thin separators.

### Components

- **Session card:** Approximately 600 × 130px with 8px corners, avatar/title row and lower counts separated by a rule.
- **Filters:** Upcoming sessions and All team dropdowns sit beside a pale search field; total session count aligns right.
- **Header actions:** Compact rounded rectangles with distinct filled/outlined states.
- **Rail:** Icon/text pairs repeat vertically, with a tinted selected Events icon and lower unread badge.

### Visual rhythm

- **Spacing:** Dense header bands contrast with a broad blank body.
- **Alignment:** Card content uses consistent insets; filter controls share one baseline.

### Responsive

- **Recommended adaptation:** Only desktop is observed. Collapse rail labels, wrap header actions and make the session card fluid.
- **Priority:** Retain draft state, timing and publish/add-session distinctions.

### Adaptation guidance

- **Preserve:** Keep event-level actions separate from individual session metadata.
- **Adapt:** Use real dates/counts and publication state; do not add sessions to fill the empty canvas.

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