Inspiration
Climate action tools often feel either too technical or too generic. We wanted to build something practical: a platform where users can quickly understand their daily carbon impact and get clear, AI-style suggestions without complexity.
What it does
EcoMind AI helps users:
- Estimate carbon footprint from everyday habits (travel, electricity, food, waste)
- Get personalized sustainability recommendations
- Classify waste with a simple upload flow (mock classifier)
- Track impact through a climate dashboard with analytics
- Stay engaged using points, badges, and a leaderboard
How we built it
We built EcoMind AI using:
- Next.js (App Router) + TypeScript
- Tailwind CSS for a clean, minimal UI
- Framer Motion for lightweight transitions
- Recharts for simple analytics visualizations
Architecture highlights:
- Modular reusable components
- Local logic for analysis and recommendations (no backend dependency required)
- Clear separation of concerns across app pages, components, and lib utilities
Challenges we ran into
- Making the app production-ready while keeping UI intentionally minimal
- Handling build and TypeScript/lint consistency across local and Vercel environments
- Balancing feature breadth (analyzer, recommendations, waste, dashboard, gamification) with maintainable code structure
Accomplishments that we're proud of
- Delivered a full end-to-end working product with multiple climate features
- Kept architecture scalable and clean for future upgrades
- Built meaningful user flows without requiring external APIs
- Successfully deployed and iterated through real build/debug cycles
What we learned
- Strong modular architecture speeds up feature delivery and debugging
- Simple rule-based AI logic can still provide clear user value in early versions
- Build pipeline reliability (TypeScript + ESLint + deployment config) is as important as feature implementation
What's next for EcoMind ai
- Integrate real AI models for smarter recommendations and contextual coaching
- Add authenticated user accounts and long-term progress tracking
- Introduce real environmental datasets (location-based and time-based insights)
UI/UX Changes: Before vs After
UX Improvements
| Aspect | Before | After | Impact |
|---|---|---|---|
| Visual Clarity | Numbered badges + emojis (visual clutter) | Clean text list | Reduced cognitive load, faster scanning |
| Information Hierarchy | 3 separate stat cards with detailed context | 4 cards with mixed data types | Better focus, clearer stat grouping |
| Trust & Transparency | Real-world claims ("23% reduction", "active users") | Explicit demo labels ("Mock", "Demo") | Honest expectations, no false claims |
| Feature Focus | Feature-centric with benefit claims | Feature-centric, functionality-first | Prevents overpromising, sets realistic scope |
| Onboarding Messaging | "Free to use · No account required" (benefit-driven) | Removed messaging | Cleaner hero section, assumes user knows format |
| Visual Hierarchy | Strong (icons + numbers guide attention) | Minimal (plain text) | Simplification vs. Visual guidance |
Summary
Better UX: Cleaner interface, fewer distractions, explicit demo status prevents user confusion Trade-off: Lost visual appeal and progressive disclosure of features through numbered flow
Built With
- next
- typescript

Log in or sign up for Devpost to join the conversation.