## Reference images

Study these alongside the description below: hierarchy, rhythm, spacing, colour. Build for the product you are asked about, using this design language.

- Component: https://kage-design-assets.t3.tigrisfiles.io/components/openwhispr-for-ios/fdca984f-87fc-4407-a067-b1821a770c20-1791957715-1.webp
- Full page it was cut from: https://kage-design-assets.t3.tigrisfiles.io/screenshots/openwhispr-for-ios/fdca984f-87fc-4407-a067-b1821a770c20-1791957682462-full.webp
- Component on Kage: https://kage.design/component/openwhispr-for-ios-hero

## Before you start
Ask what the user's product, audience, and brand are, then apply the principles below to that product rather than reproducing this reference.

Create a spacious software hero directly below the navigation. Use a two-column intro: a large, short, left-aligned headline on the left and a compact explanatory paragraph with a primary download CTA on the right. Add a small social-proof row beneath the copy, then place a large rounded product-demo visual below it. The demo should feel like an interface preview inside a vivid, softly graded blue environment, with a segmented mode switcher and a central frosted/light application panel. Use a 56–64px headline with tight line height, 18px body copy, and 15–16px button text. Keep the content in a max-width container around 860–1100px, with 48–72px vertical spacing before the demo. Use white and near-black text in the intro, blue gradients around #0878d8/#73d6ef for the visual, white translucent panels, 18–24px corner radii, and soft shadows. Make the CTA pill-shaped and clearly primary; the demo may include hoverable tabs but should remain legible and decorative on mobile.

Never: use logos, product names, copy, illustrations, or imagery from the reference.