YNAB

Priority rows, a plan total, and category funding bars create three levels of budget detail.

You Need A Budget LLC · iOS · Listing version 26.33. Publisher-provided App Store previews, reviewed 2026-09-09. Promotional framing is retained; screen order does not represent a tested flow.

Publisher previews reviewed · 2026-09-09Open full image ↗

Data visualization

Why this pattern works

Study budget home, plan editor, category funding. Compare the hierarchy and controls shown in these publisher previews, then test the corresponding behavior in your own app.

Design notes

Surface: Budget home · Plan editor · Category funding
Navigation: Home and plan surfaces separate the overview from assigning amounts to categories.
Layout: Priority rows, a plan total, and category funding bars create three levels of budget detail.
Density: Compare the space reserved for the primary task with secondary metadata. The previews retain promotional framing; evaluate target sizes in your implemented screen.
Color: White and dark blue surfaces with bright green allocation highlights.
Type: Use clear heading, body, and metadata levels. Keep interface text scalable and verify readability with the device text-size settings.
Pattern: Data visualization
States: Static publisher previews only. Loading, empty, error, offline, permission, and keyboard behavior have not been tested. Specify and verify those states in your own implementation.
Don't: Do not copy the app identity, proprietary artwork, or promotional claims. Screenshot order is not a verified flow, and the listing version does not date every image.

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: YNAB
Source: https://apps.apple.com/us/app/id1010865877
Swipefile reference: https://swipefile.design/ref/mobile-ynab/
Captured: 2026-09-09. This is a dated reference, not a claim about the current live product.
Source scope: publisher-provided App Store previews. Promotional framing is retained. These are static examples, not a tested or recorded user flow. Do not infer unseen interactions.

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

## Reference notes
- surface: Budget home · Plan editor · Category funding
- nav: Home and plan surfaces separate the overview from assigning amounts to categories.
- layout: Priority rows, a plan total, and category funding bars create three levels of budget detail.
- density: Compare the space reserved for the primary task with secondary metadata. The previews retain promotional framing; evaluate target sizes in your implemented screen.
- color: White and dark blue surfaces with bright green allocation highlights.
- typography: Use clear heading, body, and metadata levels. Keep interface text scalable and verify readability with the device text-size settings.
- pattern: Data visualization
- states: Static publisher previews only. Loading, empty, error, offline, permission, and keyboard behavior have not been tested. Specify and verify those states in your own implementation.
- dont: Do not copy the app identity, proprietary artwork, or promotional claims. Screenshot order is not a verified flow, and the listing version does not date every image.

Useful for: Study budget home, plan editor, category funding. Compare the hierarchy and controls shown in these publisher previews, then test the corresponding behavior in your own app.

## 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.
- Accessible platform-native components express the interface; use semantic HTML when the target is mobile web. 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 interaction and layout patterns below to my project. Use my own content and identity. Do not reproduce logos, proprietary copy, or brand assets.

Useful for: Study budget home, plan editor, category funding. Compare the hierarchy and controls shown in these publisher previews, then test the corresponding behavior in your own app.

YNAB

Make it your own

Keep exploring

Help improve Swipefile?