Illoca

Product ShowcaseVisit siteilloca.unseen.co

Architectural illustration turns a complex AI design product into an approachable workspace. A compact floating navigation leads directly to features, pricing, and a free trial.

Illoca — captured interface — Viewport capture · opening screen

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

AI interfaces

Why this pattern works

Architectural software launches that need to explain both the workflow and the first step.

Design notes

Mood: Warm and precise
Colors: Cream, cobalt blue, black
Type: Large restrained sans headlines and small technical labels
Layout: Centered headline above a wide architectural illustration; compact floating navigation
Motion: Static capture of a live site. Open the source to study its interactive behavior.
Texture: Fine vertical rules and flat architectural drawing
Don't: Adapt the hierarchy and visual principles to your own content; avoid copying the identity, imagery, or exact layout.

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: Illoca
Source: https://illoca.unseen.co/
Swipefile reference: https://swipefile.design/ref/awwwards-illoca/
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: Warm and precise
- colors: Cream, cobalt blue, black
- typography: Large restrained sans headlines and small technical labels
- layout: Centered headline above a wide architectural illustration; compact floating navigation
- motion: Static capture of a live site. Open the source to study its interactive behavior.
- texture: Fine vertical rules and flat architectural drawing
- dont: Adapt the hierarchy and visual principles to your own content; avoid copying the identity, imagery, or exact layout.

Useful for: Architectural software launches that need to explain both the workflow and the first step.

## 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: Architectural software launches that need to explain both the workflow and the first step.

Illoca

Make it your own

Keep exploring