← Previous26 / 34Next →

Loops Import Data

LoopsThe email platform built for SaaS

Design with AI

Create a new design inspired by Loops Import Data, 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 941 words

# Design from Reference: Loops Import Data

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

## Reference

- **Product:** Loops
- **Category:** Import & Export
- **Screenshot:** attached to this message (also available at https://media.saasframe.io/v/c1e954ae074fc5dfbed0-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
- **Character:** Minimal contact-import wizard with a pale-gray canvas, narrow white mapping card and dark navy actions.
- **Brand accent:** A small orange loop mark is the only strong warm color.
- **Scale:** The source measures 2880 × 3590 image px. Dimensions below estimate a 1440 × 1795 CSS layout at 2× scale; device ratio and zoom are unverified.

### Page composition
- **Header stack:** Centered brand symbol, Import contacts title, short subtitle and four-segment progress indicator sit above source-method tabs.
- **Source tabs:** Five plain choices span the center; Upload CSV is selected on a pale rounded background.
- **Mapping card:** A narrow approximately 400 CSS px white panel contains a title/instruction and two-column mapping list.
- **Rows:** One email column is connected, while nine further source-property rows have dark Connect actions and non-import helper text.
- **Footer:** Back/Next share a row inside the card, with a skip link below and a circular help control at the lower right.

### Information hierarchy
- **Task:** Import contacts leads; Map properties explains the current subtask.
- **Relationship:** CSV Column and Audience Field headers define source-to-destination mapping.
- **State:** The email row has an outlined linked-field control. Other rows explicitly indicate they will not be imported until connected.
- **Progression:** Next is the strongest bottom action, with Back and Skip as alternatives.
- **Evidence limit:** No import completion or contact-write outcome is shown.

### Typography
- **Family:** Neutral interface sans-serif; exact identity is unverified.
- **Title:** Approximately 32 px, bold, dark navy.
- **Card title:** Around 18–20 px, medium weight.
- **Body/rows:** Approximately 14 px with 20 px leading.
- **Headers/helper:** Small uppercase column captions and 12 px helper text are muted.

### Colors & surfaces
- **Measured base:** ICC-aware sRGB sampling yields #F9FAFB and #FFFFFF.
- **Measured foreground/action:** #0F1828 is the dark navy treatment.
- **Measured neutral:** #495564 and #687281 appear in text; #E3E7EB and #F3F4F6 define rules/selected surfaces.
- **Accent:** Orange is confined to the brand mark.
- **Depth:** Fine outlines, small corners and slight control shadows keep the page restrained.

### Components
- **Progress:** Four short rounded gray segments have one darker current segment.
- **Tabs:** Five text choices use one pale rounded active pill.
- **Mapping rows:** Thin horizontal separators divide source names and destination controls.
- **Connected field:** A small outlined rectangle includes a chain icon and Email label, with an arrow pointing toward it.
- **Connect actions:** Repeated dark buttons contain a plus and Connect caption; helper text sits directly below.
- **Navigation:** Equal-width outlined Back and dark Next buttons fill the card's bottom row.

### Visual rhythm
- **Narrow measure:** The tall card remains centered with broad blank margins.
- **Row cadence:** Consistent roughly 110 px CSS-scale rows accommodate button/helper stacks.
- **Alignment:** Source labels and destination controls keep fixed column axes.
- **Footer pause:** Skip is separated from the card by a small open gap.

### Responsive
- **Evidence limit:** Only desktop is shown; recommendations follow.
- **Card:** Use fluid width with side margins.
- **Mappings:** Stack source/destination within each row when necessary.
- **Tabs/actions:** Allow tab scrolling and retain readable progression controls.

### Adaptation guidance
- **Reusable pattern:** Make source-to-field relationships explicit before importing.
- **State clarity:** Clearly distinguish connected and excluded properties.
- **Accessibility:** Label each mapping action with its source property and announce connection changes.
- **Data discipline:** Do not treat a mapping preview as a completed import.

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