Skip to main content
Prompts App Store Screenshots Gallery Generator

developer coding user risk: low

App Store Screenshots Gallery Generator

Instructs the model to generate a single production-ready HTML file for an app screenshots gallery page, featuring a responsive masonry grid, design tokens for colors and typograph…

PROMPT

# App Store Screenshots Gallery Generator

**Create a professional, production-ready screenshots gallery for an iOS/macOS/Android app that looks like it was designed by the top 1% of app developers.**

## Context

You are building a screenshots gallery page for an app. The project has screenshots in a folder (typically `screenshots/`, `fastlane/screenshots/`, or similar). The gallery should be a single HTML file that can be deployed to Netlify, Vercel, or any static host.

## Requirements

### 1. Design System Foundation

Create CSS custom properties (design tokens) for:

- **Colors**: Primary palette (50-900 shades), secondary/accent palette, neutral grays (50-900)
- **Surfaces**: Three surface levels (surface-1, surface-2, surface-3)
- **Typography**: Two-font stack (mono for UI elements, sans for body)
- **Spacing**: Consistent scale (4px base)
- **Borders**: Radius scale (sm, md, lg, xl, 2xl, 3xl)
- **Shadows**: Five elevation levels (sm, md, lg, xl, 2xl)
- **Transitions**: Three speeds (fast: 150ms, normal: 300ms, smooth: 400ms with cubic-bezier)

### 2. Layout Architecture

- **Container**: Max-width 1600px, centered, with responsive padding
- **Grid**: Masonry-style responsive grid using `grid-template-columns: repeat(auto-fill, minmax(340px, 1fr))`
- **Gap**: 2rem on desktop, 1.5rem tablet, 1rem mobile
- **Card aspect ratio**: Maintain consistent screenshot presentation

### 3. Header Section

- **App badge**: Small pill-shaped badge with icon and "IOS APPLICATION" or platform text
- **Title**: Large, bold app name with gradient text treatment
- **Subtitle**: One-line description mentioning key technologies and features
- **Background**: Subtle grid pattern overlay for depth
- **Padding**: Reduced vertical padding (3rem top, 2rem bottom) for compact feel

### 4. Screenshot Cards

Each card should have:

- **Container**: White/off-white background, rounded corners (2xl), subtle shadow
- **Image container**: Gradient background, centered screenshot with white border (8px)
- **Hover effects**:
  - Card lifts (-8px translateY) with enhanced shadow
  - Screenshot scales (1.04) with slight rotation (0.5deg)
  - Top border appears (gradient bar)
  - Radial glow overlay fades in
- **Metadata bar**:
  - Number badge (gradient background, 26px square)
  - Device name (uppercase, small font, mono font)
- **Title**: Bold, mono font, 1rem
- **Description**: One-line caption, smaller font, subtle color

### 5. User Journey Ordering

Order screenshots by how users experience the app:

1. **Login/Onboarding** - First screen users see
2. **Dashboard/Home** - Main landing after login
3. **Primary feature views** - Core app functionality
4. **Settings/Configuration** - Customization screens
5. **Permissions/Integrations** - HealthKit, notifications, etc.
6. **Advanced features** - Sync, sharing, cloud features
7. **Analytics/Reports** - Data visualization screens
8. **Archive/History** - Historical data views

### 6. Animations

- **Entrance**: Staggered fade-in with translateY (0.1s delays between cards)
- **Hover**: Smooth cubic-bezier easing (0.16, 1, 0.3, 1)
- **Scroll**: IntersectionObserver to trigger animations when cards enter viewport
- **Performance**: Use `will-change` for transform and opacity

### 7. Footer

- **Background**: Dark (neutral-900) with subtle gradient overlay
- **Border radius**: Top corners only (2xl)
- **Content**: Minimal metadata (device, date, status) with icons
- **Spacing**: Compact (2rem padding)

### 8. Responsive Breakpoints

- **Desktop** (>1280px): 4-5 columns
- **Tablet** (768-1280px): 2-3 columns
- **Mobile** (<768px): 1 column, reduced padding throughout

### 9. Technical Requirements

- **Single HTML file**: All CSS inline in `<style>` tag
- **External dependencies only**:
  - Pico.css (minimal CSS framework)
  - Font Awesome (icons)
  - Google Fonts (Inter + IBM Plex Mono)
  - Animate.css (optional, for additional animations)
- **No build step**: Must work as static HTML
- **Performance**: Optimized animations, no layout shift
- **Accessibility**: Semantic HTML, alt text on images

### 10. Polish Details

- **Subtle gradients**: Background radials for depth (not overwhelming)
- **Border treatment**: 1px solid with alpha transparency
- **Shadow layering**: Multiple shadow values for depth
- **Typography**: Tight letter-spacing on headings (-0.03em)
- **Color consistency**: Use design tokens everywhere, no hardcoded values
- **Image presentation**: White border around screenshots for device frame illusion

## Output Format

Generate a single `index.html` file with:

1. Complete HTML structure
2. Inline CSS with design tokens
3. JavaScript for scroll animations (IntersectionObserver)
4. All screenshot cards with proper metadata
5. Responsive design for all screen sizes

## Example Screenshot Card Structure

```html
<div class="screenshot-card">
    <div class="screenshot-img-container">
        <img src="screenshot-name.png" alt="Description" class="screenshot-img">
    </div>
    <div class="screenshot-info">
        <div class="screenshot-meta">
            <div class="screenshot-number">1</div>
            <div class="screenshot-device">iPhone 17 Pro Max</div>
        </div>
        <h3 class="screenshot-title">Screen Title</h3>
        <p class="screenshot-desc">One-line caption</p>
    </div>
</div>
```

## Key Differentiators from "AI-looking" Galleries

❌ **Avoid**:
- Excessive gradients and colors
- Large stat cards that waste space
- Verbose descriptions and feature lists
- Section dividers and category headers
- Overwhelming animations
- Inconsistent spacing
- Generic stock photography style

✅ **Emulate**:
- Apple App Store product pages
- Linear, Raycast, Superhuman marketing sites
- Minimalist, content-first design
- Subtle, refined interactions
- Consistent visual rhythm
- Typography-driven hierarchy
- White space as design element

## Deployment Notes

- Gallery should deploy to `project-root/screenshots-gallery/` or similar
- Include `.netlify` folder with `netlify.toml` for configuration
- All screenshots should be in the same folder as `index.html`
- No build process required - pure static HTML

---

**Usage**: Copy this prompt and provide it to an AI assistant along with:
1. The list of screenshot files in your project
2. Your app name and one-line description
3. The platform (iOS, macOS, Android, web)
4. Key technologies used (SwiftUI, React Native, Flutter, etc.)

The AI will generate a production-ready gallery that looks professionally designed.

INPUTS

screenshot_files REQUIRED

List of screenshot image files to include in the gallery

e.g. login.png, dashboard.png, settings.png

app_name REQUIRED

Name of the app for the header title

e.g. MyApp

app_description REQUIRED

One-line description mentioning key technologies and features

e.g. Built with SwiftUI and HealthKit for seamless fitness tracking.

platform REQUIRED

Platform of the app (iOS, macOS, Android, web)

e.g. iOS

technologies REQUIRED

Key technologies used in the app

e.g. SwiftUI, HealthKit

REQUIRED CONTEXT

  • list of screenshot files
  • app name
  • one-line description
  • platform
  • key technologies

OPTIONAL CONTEXT

  • screenshot folder path

ROLES & RULES

  1. Create CSS custom properties for colors, surfaces, typography, spacing, borders, shadows, and transitions.
  2. Use masonry-style responsive grid.
  3. Include app badge, title, subtitle in header.
  4. Implement screenshot cards with image container, metadata bar, title, description.
  5. Order screenshots by user journey.
  6. Add entrance, hover, and scroll animations.
  7. Make footer with dark background.
  8. Ensure responsive breakpoints.
  9. Use single HTML file with inline CSS.
  10. Use only Pico.css, Font Awesome, Google Fonts, Animate.css as external dependencies.
  11. No build step.
  12. Include polish details like subtle gradients, accessibility.
  13. Avoid excessive gradients and colors.
  14. Avoid large stat cards that waste space.
  15. Avoid verbose descriptions and feature lists.
  16. Avoid section dividers and category headers.
  17. Avoid overwhelming animations.
  18. Avoid inconsistent spacing.
  19. Avoid generic stock photography style.

EXPECTED OUTPUT

Format
html
Schema
html · Complete HTML structure, Inline CSS with design tokens, JavaScript for scroll animations (IntersectionObserver), All screenshot cards with proper metadata, Responsive design for all screen sizes
Constraints
  • single HTML file
  • inline CSS with design tokens
  • JavaScript for scroll animations
  • responsive design
  • semantic HTML
  • all screenshot cards with metadata

SUCCESS CRITERIA

  • Create professional production-ready screenshots gallery.
  • Follow design system foundation.
  • Implement layout architecture.
  • Include header section.
  • Design screenshot cards with hover effects.
  • Order by user journey.
  • Add animations and performance optimizations.
  • Ensure responsive design.
  • Meet technical requirements.
  • Apply polish details.
  • Emulate top app store pages.

FAILURE MODES

  • Excessive gradients and colors.
  • Large stat cards wasting space.
  • Verbose descriptions.
  • Section dividers and category headers.
  • Overwhelming animations.
  • Inconsistent spacing.
  • Generic stock photography style.
  • Build steps or non-static HTML.
  • Hardcoded values instead of design tokens.
  • Poor accessibility or performance.

EXAMPLES

Includes one example screenshot card HTML structure.

CAVEATS

Dependencies
  • List of screenshot files in the project.
  • App name and one-line description.
  • Platform (iOS, macOS, Android, web).
  • Key technologies used (SwiftUI, React Native, Flutter, etc.).
Missing context
  • List of screenshot files
  • App name
  • One-line description
  • Platform (iOS/macOS/Android/web)
  • Key technologies used
Ambiguities
  • Unclear how to generate 'proper metadata' (titles, descriptions, device names, user journey ordering) for screenshots without specific details provided.
  • Deployment notes mention including '.netlify folder with netlify.toml', but output format specifies only a single 'index.html' file.

QUALITY

OVERALL
0.92
CLARITY
0.95
SPECIFICITY
0.95
REUSABILITY
0.85
COMPLETENESS
0.90

IMPROVEMENT SUGGESTIONS

  • Introduce placeholders like {APP_NAME}, {DESCRIPTION}, {PLATFORM}, {SCREENSHOTS} to enhance reusability as a template.
  • Clarify metadata generation process, e.g., 'Infer device from filename patterns (e.g., iphone14-pro.png -> iPhone 14 Pro); assign titles and descriptions based on user journey categories.'
  • Resolve output scope: either expand to generate a zip/tar with index.html and .netlify.toml, or remove deployment folder mention.
  • Add a small example of user input (screenshot list, app details) and corresponding generated card HTML.

USAGE

Copy the prompt above and paste it into your AI of choice — Claude, ChatGPT, Gemini, or anywhere else you're working. Replace any placeholder sections with your own context, then ask for the output.

MORE FOR DEVELOPER