Case study — visual materials to produce
Each case-study page now has four visual slots. Fill them via frontmatter (cover, gallery: [{src, alt, caption}], video: {src, poster}). Until filled, each slot shows a clean labeled placeholder. Below is exactly what to make per project.
The four slots (same for every case study)
- Hero cover — one motion cover (mp4/webm loop) OR a strong hero still (16:9). Motion preferred (see cover-motion-prompts).
- Key screens — 3–6 polished UI screens (the decisive ones), each with a one-line caption that states the decision, not the feature.
- Flow / diagram — one user-flow or IA/architecture diagram (clean, light, on-brand).
- Walkthrough — optional 20–40s screen recording or prototype clip.
Keep assets light (<2–3 MB each). Consistent crop, light background, same caption type across all projects so the set feels cohesive.
Zevo (flagship — finance × tech)
- Cover: contactless-unlock motion loop (prompt already written).
- Key screens (5): booking flow (3-tap), vehicle detail (charge/host/photos), the linear unlock sequence, owner earnings dashboard, payout/deposit screen.
- Diagram: the contactless-unlock flow with failure/recovery branches (your core trade-off — show it).
- Walkthrough: export a 20–30s clip of the booking→unlock flow from the Figma prototype.
Wire (enterprise / B2B)
- Cover: hero still or subtle motion of the plan-comparison table.
- Key screens (4): plan comparison (progressive disclosure), pricing transparency, checkout step with persistent order summary, confirmation state.
- Diagram: the two-buyer split (enterprise procurement vs privacy individual) mapped to one comparison surface.
- Walkthrough: optional checkout walkthrough.
Samsung eShop (commerce)
- Cover: product page hero (specs-upfront) still or motion.
- Key screens (4): product page with specs surfaced, comparison, stripped checkout, mobile layout.
- Diagram: the dual systems-of-record architecture (ERP stock + Samsung CRM pricing → one storefront).
- Walkthrough: optional.
Agents4.fun (onchain analytics + execution)
- Cover: dashboard “live” motion loop (prompt already written for Agent4).
- Key screens (4): agent state/overview, analytics view, value-movement / execution view, onchain audit trail.
- Diagram: agent perceive → decide → act → settle-on-Ethereum flow with the audit trail.
- Walkthrough: short live screen capture of the dashboard.
Production order (suggested)
- Zevo (flagship, needed for Solana app) — cover + 5 screens + unlock diagram + proto clip.
- Agents4.fun — dashboard screens + onchain flow diagram.
- Wire — comparison + checkout screens + two-buyer diagram.
- Samsung — product/checkout screens + architecture diagram.
For each: drop files in foogy.dev/public/ and tell me — I wire them into the frontmatter and they replace the placeholders.