Apple-Inspired

You are building a web application using Next.js with Tailwind.
Read existing project instructions and reuse installed components where available.

## Project
Project brief: Not specified
Target users: Not specified
Page purpose: SaaS
Framework: Next.js
CSS approach: Tailwind
UI library: Custom / no library
Tone: Professional

## Visual direction
Base theme: Apple-Inspired (visual-style)
- Heavy use of whitespace and negative space
- Large hero imagery with text overlays
- Subtle animations and transitions
- Rounded rectangles everywhere
- Clean sans-serif typography
- Product-focused minimalism

## Resolved style
Use this final token set. It already includes the selected layers. These values take precedence over conflicting base characteristics.
Color palette: primary #0071E3, secondary #86868B, accent #AC39FF, background #FFFFFF, text #1D1D1F
Typography: SF Pro Display for headings, SF Pro Text for body text
Load the declared fonts with the required weights. Use system fallbacks when a font is unavailable.
```css
:root {
  --tx-surface-bg: #FFFFFF;
  --tx-font-heading: "SF Pro Display", sans-serif;
  --tx-font-body: "SF Pro Text", sans-serif;
  --tx-surface-bg-image: none;
  --tx-card-bg: #FFFFFF;
  --tx-card-border: rgba(0,0,0,0.06);
  --tx-card-border-width: 1px;
  --tx-card-radius: 1.25rem;
  --tx-card-shadow: 0 2px 12px rgba(0,0,0,0.06);
  --tx-card-backdrop-blur: 0px;
  --tx-card-border-hover: rgba(0,113,227,0.2);
  --tx-card-shadow-hover: 0 4px 20px rgba(0,0,0,0.08);
  --tx-font-heading-weight: 600;
  --tx-font-body-weight: 400;
  --tx-text-muted: rgba(29,29,31,0.6);
  --tx-text-subtle: rgba(29,29,31,0.4);
  --tx-link-color: #0071E3;
  --tx-button-radius: 9999px;
  --tx-input-bg: #FFFFFF;
  --tx-input-border: rgba(0,0,0,0.1);
  --tx-text: #1D1D1F;
  --tx-primary: #0071E3;
  --tx-secondary: #86868B;
  --tx-accent: #AC39FF;
  --tx-media-filter: none;
}
```
Use the CSS variables in your own components. Apply the heading and body font variables to their respective elements.

## Layout
- Use generous spacing, large product headings, and clearly separated sections.

## Interaction
- Use short opacity and position transitions without delaying navigation.

## Suitability notes
Use these limitations to assess the chosen page purpose. Explain any mismatch before applying an unsuitable treatment.
- Apple-Inspired: Interfaces that need many controls visible at once.

## Components
Generate the following components in this style:
- Hero
- Navbar
- Cards
- Footer

## Quality requirements
Choose section order and visual emphasis from the real content and page purpose. Add only sections needed for the task.
Use supplied content. Label sample data. Do not invent testimonials, customer logos, statistics, or compliance claims.
Every interactive control must perform its declared action or be clearly labeled as a demo.
Include loading, empty, error, success, disabled, and focus states where applicable.
Use semantic HTML, visible keyboard focus, readable text contrast, and labeled form fields.
Ensure responsive design (mobile-first). Preserve reading order and avoid horizontal page overflow.
Respect prefers-reduced-motion. Keep essential content visible when animations are disabled.

## Verification
Check representative desktop and mobile widths, keyboard interaction, and relevant component states. Run available project checks and report what was actually verified.
Use Tailwind utility classes with the declared tokens.
Product context is incomplete. Label assumptions and treat the result as a draft until the missing context is supplied.