Cooper AI Chat - Mobile App Exploration

Mobile apps reference. Small lavender cards and clear conversational actions organize an AI assistant across home, activity, and plan screens. Credit: Paperpillar. Designer-published mobile apps presentation on Dribbble; concept or case-study artwork, implementation not independently verified. Curated for the MotionSites-inspired batch (2026-10-10).

Design presentation reviewed · 2026-10-11Open full image ↗

Forms & onboarding

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 withAny AI toolCodexClaudeCursorChatGPTGeminiv0 / LovableI want toBuild a screenAudit my UIWrite a design brief

Tech stackUse the existing project stackReact / Next.jsAstroVue / NuxtSvelte / SvelteKitHTML / CSS / JavaScriptSwiftUIFlutter

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: Cooper AI Chat - Mobile App Exploration Source: https://dribbble.com/shots/24133515-Cooper-AI-Chat-Mobile-App-Exploration Swipefile reference: https://swipefile.design/ref/ms26-mobile-24133515-cooper-ai-chat-mobile-app-exploration/ Captured: 2026-10-11. This is a dated reference, not a claim about the current live product. Source scope: static designer or award presentation. This may be concept or case-study artwork. Do not infer working features, unseen screens, or tested 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 Mobile apps reference. Small lavender cards and clear conversational actions organize an AI assistant across home, activity, and plan screens. Credit: Paperpillar. Designer-published mobile apps presentation on Dribbble; concept or case-study artwork, implementation not independently verified. Curated for the MotionSites-inspired batch (2026-10-10). ## 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.

Copy promptDownload .md

Assembled in your browser. No API key or AI request needed. Changing the fields refreshes the preview.