← Previous11 / 31Next →

Privy Onboarding Create First App

PrivyWallet and stablecoin infrastructure to build wallets, hold crypto and move money with programmable finance

Design with AI

Create a new design inspired by Privy Onboarding Create First App, 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 822 words

# Design from Reference: Privy Onboarding Create First App

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

## Reference

- **Product:** Privy
- **Category:** Account Setup
- **Screenshot:** attached to this message (also available at https://media.saasframe.io/v/eab1a0e7e477a07dd876-1600.webp)
- **Source:** https://dashboard.privy.io/welcome

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

## Privy — shared visual language

- **Theme**: crisp light fintech site with soft lilac-to-violet gradient imagery, alternating with near-black (#010110 / #111117) sections for performance and security. A small "privy | a stripe company" lockup in the top bar.
- **Typography**: geometric grotesk display faces at weight 400: FFF Acid Grotesk for product pages (H1 58px/64px, -1.74px; H2 42px/48px, -1.26px) and ABC Favorit for campaign pages (H1 78px/78px, -4.68px; H2 56px/58px). Inter for UI and body (14–20px), small uppercase eyebrows in Inter 12px w600 with 1.2px tracking, #70707D.
- **Colors**: near-black #010110 text and primary buttons, white and #F8F9FC surfaces, grey #70707D secondary text; lilac/periwinkle gradients (#C4D4F6, violet, pink) inside product shots; coral as the brand accent in logo usage; customer cards in each customer's colour.
- **Components**: pill buttons 36px with 100px radius (black "Get started", outlined "Talk to sales"); product mockups (wallet balances, treasury dashboards, approvals) floating on gradient panels; metric rows ("200M+", "$25B+", "99.99%"); case-study cards with "Challenge / Solution"; FAQ lists; a five-column footer signed "Technical decisions are moral decisions."
- **Layout**: centred 1200px content; heroes either split (copy left, gradient visual right) or centred over a gradient product shot; feature rows alternate image and copy.
- **Tone**: calm and confident, infrastructure language ("Build products that hold, move, and grow digital assets").

## Privy dashboard (dashboard.privy.io) — product UI

- **Auth and onboarding**: white cards on a grainy lilac gradient (#FEF4FF to #E2E3F0), Inter 30px/42px w600 titles in #040217, 44px black pill buttons (#020713, 9999px radius), inputs with inline "Required" tags, violet links #5B4FFF.
- **Dashboard theme**: dark navy, page #020713, cards #0E1522 with #384060 / #1A2230 borders, text #F8F8F8 / #C0C4CC / #9BA2AE, violet accent #8B86FF for primary buttons and #A29EFF for links; green development-mode banner (#273517).
- **Shell**: ~280px sidebar with app switcher and collapsible groups (App settings, Wallet infrastructure, Financial flows, User management); top bar with "Search for anything ⌘K", Docs, Support and avatar; content column ~896px.
- **Components**: Inter 24px w600 page titles, underline tabs, toggle rows for settings, 6px-radius cards, promo panels with numbered "How it works" steps and an illustration on the right.

### Overall aesthetic
- **Style:** last onboarding card, same frame as the questions.

### Page composition
- **Card:** small status label, H1, one input, button, skip link.

### Typography
- **Title:** Inter 30px/42px w600, #040217. **Label:** 15px.

### Colors & surfaces
- **Base:** white card on grain gradient; button #020713.

### Components
- **Input:** with inline "Required" tag.
- **Skip link:** under the primary button.

### Responsive
- **Desktop only:** captured at 1440px.

### Adaptation guidance
- **Lesson:** end onboarding with the first object creation, but keep a skip so exploration is possible.

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

Visit live page

Patterns

Add Item
Text Input
Wizard

Tech Stack

Framer

Part of flow

Privy Onboarding

Added on

November 12, 2026

A completion label above the next task

After the three questions, Privy's onboarding card switches its top label from the step counter to "You're all set!" and moves straight to the next task: "Start by creating your first application." The back arrow disappears, which signals that the profile part is finished.

One field to name the app

A single "Name your app" field with a small "Required" tag sits under the title, in the same style as the organization field of step one. The black "Create app" pill stays pinned at the bottom of the card, in exactly the same place as "Next" and "Accept and continue" before it.

Creation is optional

A plain "Skip app creation" link below the button lets you enter the dashboard without creating anything, so the onboarding never blocks someone who only wants to look around first.