Loops

Document MinimalVisit siteloops.so

A deliberately small headline and sparse navigation leave room for a quiet workflow illustration, giving the email product a lightweight feel.

Loops — captured interface — Viewport capture · opening screen

Source capture · 2026-09-05Open full image ↗

Why this pattern works

Focused SaaS tools that benefit from a calm, low-density introduction.

Design notes

Mood: Quiet and lightweight
Colors: White, pale gray, small orange accents
Type: Small restrained sans text throughout
Layout: Small introduction near the upper center, broad workflow diagram below
Motion: Static opening-screen capture. Visit the source to study transitions and interactive behavior.
Texture: Thin outlined email panels and abundant white space
Don't: Adapt the hierarchy to your own product and content; use your own identity and imagery.

Make it your own

Turn this reference into a useful brief for your project. Copy it into the AI tool you already use.

Your project

Use withI want to

Tech stack

Add constraints

What should the tool respect?

Preview & edit prompt

Prompt text

# My project
[Describe the product, audience, and screen you want to improve]

Stack: Use the existing project stack
Task: Implement the interface and verify the result in the existing project.

## Tool guidance (Any AI tool)
Use available project tools to inspect, implement, and test. State any unavailable capabilities.

# Design reference: Loops
Source: https://loops.so/
Swipefile reference: https://swipefile.design/ref/saas-loops/
Captured: 2026-09-05. This is a dated reference, not a claim about the current live product.
Capture scope: one viewport. Do not infer unseen page sections or a complete user flow.

## Objective
Adapt the visual principles below to my project. Use my own content and identity. Do not reproduce logos, proprietary copy, or brand assets.

## Reference notes
- mood: Quiet and lightweight
- colors: White, pale gray, small orange accents
- typography: Small restrained sans text throughout
- layout: Small introduction near the upper center, broad workflow diagram below
- motion: Static opening-screen capture. Visit the source to study transitions and interactive behavior.
- texture: Thin outlined email panels and abundant white space
- dont: Adapt the hierarchy to your own product and content; use your own identity and imagery.

Useful for: Focused SaaS tools that benefit from a calm, low-density introduction.

## Acceptance criteria
- Existing project conventions, design tokens, working functionality, and unrelated changes are preserved.
- Two or three reference principles clearly support the user's task; conflicts are resolved in favor of usability and the existing product.
- Reusable components and semantic HTML express the interface. Available licensed assets are used; important UI text is never rendered as a bitmap.
- Every visible control has a defined behavior. Loading, empty, error, success, disabled, and long-content states are specified where relevant. Demo data is clearly labeled.
- Navigation and content adapt at 375px, 768px, and 1440px without horizontal page overflow. Keyboard use, visible focus, labeled inputs, at least 44px touch targets, readable contrast, and reduced motion are supported.
- Verification distinguishes rendered behavior from proposals and identifies anything still requiring a backend or external service.

## Quality bar
Clear hierarchy, consistent spacing, restrained surfaces, and purposeful motion. Avoid decorative gradients, excessive cards, placeholder buttons, and invented metrics unless the project calls for them. Do not claim a feature is connected or tested without evidence.

Assembled in your browser. No API key or AI request needed. Changing the fields refreshes the preview.

## Objective
Adapt the visual principles below to my project. Use my own content and identity. Do not reproduce logos, proprietary copy, or brand assets.

Useful for: Focused SaaS tools that benefit from a calm, low-density introduction.

Loops

Make it your own

Keep exploring