# AI-Driven Design Brief Session Sat, 15 Mar 25 ## 1. Overall Context & Purpose - **Session Goal**: Kick off the cohort’s mobile app design assignment. - **Key Focus**: Create a _practical, demo-ready_ mobile app concept in a limited timeframe. - **Difference From Previous Project**: Unlike the website design assignment (which used existing startups’ websites), this is about building a _brand-new app_ or substantially refining an early-stage idea—especially using AI features. ## 2. Why Mobile Apps Matter Again - **Renewed Interest**: Despite the slowdown in users downloading new apps, _AI capabilities_ have revived possibilities on mobile. - **New Categories**: AI unlocks features (personalized, adaptive, predictive) that were _not feasible_ 2–3 years ago. - **Opportunities for Designers**: Many established designers are still not working with AI tools; _learning and showcasing AI integrations_ can give you a competitive edge. ## 3. Integrating AI into the App - **Not a Separate “Field”**: There’s no formal “AX design” track yet, but AI can transform user flows in any vertical. - **Core Principle**: Still about user problems. AI is just an _enabler_—ensure your design solves meaningful needs. - **Examples**: - AI-driven mental health or therapy features (empathy-based, real-time responses). - Enhanced personalization (plant care, language learning, relationship advice). - Intelligent automation (finance, supply chain, or property management). ## 4. The Briefs: Selection & Customization - **Multiple Briefs Provided**: Some are _existing early-stage startups_ from Y Combinator; others are _“wildcard” briefs_ with fresh AI angles. - **Freedom to Adapt**: You can choose a brief, customize its scope, and even localize it (e.g., adapting a US-based concept to the Indian market). - **Advice**: - Pick a brief you’re _personally excited_ about—motivation helps you finish strong. - Don’t shy away from “wildcard” ideas; those often allow _more creativity_ if you can handle open-endedness. ## 5. Scoping the Project (Must/Should/Could) - **Must-Haves**: Identify the _core feature(s)_ that define the app. Focus on the essential user flow that demonstrates real value (e.g., the primary action or interaction). - **Should-Haves**: Secondary flows or features that improve the experience but aren’t critical. Include them if time permits. - **Could-Haves**: Tertiary ideas that are “nice to have” if there’s extra bandwidth. Do not let them derail your core must-haves. ## 6. Designing the Core Flow - **Focus on Tangible Usefulness**: A _solid core flow_ beats a scattered set of incomplete screens. - **Avoid Overkill**: Don’t devote all your time designing only login flows; _demonstrate the real functionality_ that would matter to a user. - **Information Architecture**: - Think about tabs, navigation patterns, or primary CTA placements based on _common mobile UX patterns_. - Borrow standard flows from existing apps you use daily; adapt them to your concept. ## 7. Research & References - **App Store & Play Store**: Best for discovering analogous apps or UX patterns if exact references don’t exist. - **AI Tools (ChatGPT, Claude, etc.)**: - For brainstorming ideas, user flows, or referencing existing solutions. - Use them to _unblock_ or _supplement_ your ideation, not to replace your own decision-making. - **Look at Comparable Industries**: If your concept is entirely new, find partial overlaps (e.g., therapy apps → mental health apps; vintage e-commerce → standard e-commerce flows). ## 8. Visuals & Branding - **Pragmatic Over Polish**: Mobile apps are _highly interaction-driven_. Aim for a clear, accessible interface. - **Illustrations & AI-Generated Art**: - If needed, _use AI_ to generate consistent illustrations quickly. - Leverage design systems or existing brand styles if you’re working on an already established startup. - **Balance**: Keep the UI neat, on-brand, and supportive of the core interactions. ## 9. B2B vs. B2C Considerations - **B2B**: Often perceived as less “flashy,” but can have _clearer functional flows_. - **B2C**: Usually more _visually driven_, requires strong user engagement hooks. - **Recommendation**: Choose what you’ll be _excited to complete_. Doing a thorough job on a well-scoped B2C or B2B use case can look equally impressive in a portfolio. ## 10. Q&A & Common Challenges 1. **Number of Screens?** - No fixed count. Focus on _complete, meaningful user flows_ rather than just login screens. 2. **Inspiration for Unique Features?** - Use first-principles thinking. Combine known patterns with _creative problem-solving_ for the new AI-driven elements. 3. **Target Audience?** - If it’s broad (like a consumer app), start by defining the _most urgent user group_ or _early adopters_. 4. **Case Study Presentation** - Demonstrate how you tackled the _core problem_, your reasoning, design decisions, and final prototype. 5. **Portfolio Relevance** - Any well-executed design (showing your process + skill) can impress. _Depth and clarity_ in how you solved user needs is critical. ## 11. Next Steps & Action Items 1. **Pick Your Brief** - Decide quickly to leave enough time for wireframing, prototyping, and iteration. 2. **Clarify Core Use Case** - Write a short PRD (Product Requirements Document) or outline. Focus on your must-have features. 3. **Research & Brainstorm** - Search analogous solutions, or chat with AI to gather references and user flow ideas. - Look at real apps on your phone for _navigational and structural patterns_. 4. **Begin Wireframes & MVP Flow** - Sketch or wireframe _the main user journey_ before perfecting visuals. - Validate if the flow genuinely solves the stated need. 5. **Prototype & Get Feedback** - Create a clickable prototype (Figma, etc.). - Share with peers or mentors for early feedback. 6. **Iterate & Polish** - Refine based on feedback, ensuring the final deliverable is _demo-ready_. --- **Use these notes as a blueprint to stay on track, focus on the right priorities, and make your final app design both _innovative_ (through AI) and _practically valuable_ to users.**