MENTTA - Crisis Mental Health Support at 3 AM
Inspiration
In my social environment, I saw people who were psychologically unwell, and I wanted to help them and myself as well because we weren't allowed to go to a psychologist or anything similar.
At the same time, I noticed that many young people were already talking to AIs, so Mentta was born from that idea — combining the comfort and accessibility of AI with the real need for emotional support.
The Problem We Saw:
- Friends struggling with mental health, no access to therapy
- Professional help too expensive or unavailable
- Late nights when suffering feels strongest and no help exists
- Young people already comfortable talking to AI chatbots
- Stigma preventing people from seeking help
Our "Why": We couldn't access professional help ourselves, but we could build it for others. If people talk to AI already, why not make that AI connection lead to real support?
What It Does
Mentta provides a safe space where young people can talk, reflect, and receive emotional support through AI.
Created after noticing that many people struggle psychologically without access to professional help, especially during late nights and early mornings when suffering often feels strongest and no psychologist is available — while many young people already feel comfortable talking to AIs.
Core Features:
| Feature | Description |
|---|---|
| 24/7 AI Support | Talk anytime, day or night — especially when you need it most |
| Safe & Judgment-Free | Complete privacy, no judgment, no pressure |
| Reflection Tools | Guided journaling and emotional tracking |
| Emotion Recognition | AI understands your emotional state and responds appropriately |
| Resource Library | Mental health tips, coping strategies, self-care guides |
| Chat History | Track your progress over time |
| Bilingual Support | Spanish and English (for wider reach) |
| Crisis Detection | Identifies when you need human professional help |
What Makes Mentta Different:
Always Available — 24/7 AM support when traditional therapy is closed No Cost Barrier — Free access to essential emotional support No Stigma — Talk to AI first, no judgment before connecting with professionals Young People First — Designed for how young people actually communicate Accessible — Works on any phone, anywhere
🛠️ How We Built It
The Development Journey:
Day 1: Clarity & Planning
- Started confused about the exact idea
- Took a full day to clearly define what Mentta would be
- Planned the technical architecture and task breakdown
- Divided responsibilities: Backend vs Frontend
Days 2-8: Core Development
Backend Development (Teammate): Built using Antigravity
- API endpoints for chat functionality
- Database for storing conversations
- Bilingual support implementation
- User authentication
Frontend Development : Created the user interface
- Chat interface
- User dashboard
- Settings and preferences
Daily Goals System: Broke down large tasks into daily achievable goals
- Kept team motivated with visible progress
- Made debugging easier with incremental builds
- Stayed on schedule with daily commits
Days 9-10: Testing & Feedback
- Shared project with trusted people for honest feedback
- Got valuable bug reports
- Received UX improvement suggestions
- Identified missing features
- Fixed all reported issues
- Polished the overall experience
- Refined UI/UX for crisis scenarios
Day 11-12: Demo & Submission
- Created professional 60-second demo video
- Showed real user journey
- Demonstrated crisis support workflow
- Highlighted impact potential
- Final quality checks
- Submitted to hackathon
⚠️ Challenges We Ran Into
🔴 Challenge 1: Building a Bilingual Platform
The Problem: Making Mentta work seamlessly in both Spanish and English without doubling development time.
What We Did:
- Implemented a translation system that works on both frontend and backend
- Designed UI that adapts to different text lengths
- Tested thoroughly in both languages
- Created separate language databases/APIs
Lesson Learned: Bilingual support must be built in, not added later. It affects every single component.
🔴 Challenge 2: Team Member with Limited Coding Experience
The Problem: One teammate had limited coding experience and had to learn fundamentals from scratch during development.
What We Did:
- They already had "vibe coding" experience (understanding code logic intuitively)
- Paired programming sessions
- Broke down complex tasks into simple steps
- Lots of documentation and comments
- Encouraged asking questions
- Celebrated small wins
How They Adapted: "Vibe coding" knowledge translated well. They understood the logic even without syntax mastery. Learned by doing, not just reading.
Lesson Learned: You don't need to be an expert to start. Willingness to learn matters more than starting knowledge.
🔴 Challenge 3. Learning Git for Collaboration
The Problem: Two developers working on the same project needed a way to merge code without losing work or creating conflicts.
What We Did:
- Learned Git fundamentals (branches, commits, merges)
- Set up GitHub repository
- Established workflow: feature branches → pull requests → reviews → merge
- Used clear commit messages
- Resolved merge conflicts together
Result: Git improved our workflow significantly. We could work in parallel without stepping on each other's toes.
Lesson Learned: Version control isn't optional for teams. It's fundamental. Learning it early saved hours of frustration.
🏆 Accomplishments We're Proud Of
✅ We Finished It
Despite facing multiple challenges and one team member learning to code during development, we shipped a complete, working product in one week.
- ✔️ Full app functionality — Chat, history, settings all working
- ✔️ Bilingual support — Seamless Spanish/English switching
- ✔️ Professional demo — 60-second video showing real value
- ✔️ Zero critical bugs — Thoroughly tested before submission
✅ Real Human Impact
This isn't just a tech project — it can actually help people.
- 👥 Provides support when traditional therapy is unavailable
- 🌙 Available at 24/7
- 💰 Free access removes financial barriers
- 🧠 Designed for how young people actually think and communicate
✅ We Never Gave Up
Despite difficulties:
| Challenge | Status |
|---|---|
| Multiple users system | ✅ Overcame |
| Bilingual platform | ✅ Implemented |
| Psychologist matching | ✅ Designed |
| Learning coding mid-project | ✅ Learned on the job |
| Learning Git | ✅ Mastered |
| Time pressure | ✅ Stayed focused |
✅ We Learned Fast
From confusion on Day 1 to finished product on Day 12:
- 📚 Learned multiple new technologies
- 🤝 Learned to work as an effective team
- 🔧 Learned Git from scratch
- 💪 Proved we could handle pressure and complexity
✅ We Built Something Meaningful
Most importantly:
We created a project that can help many people, especially in these times, serving as a small but meaningful contribution of support to humanity.
That's what we're most proud of.
📚 What We Learned
💡 About Ideas
#1: Not All Ideas Are Equal
- Lots of great ideas exist
- But a truly GOOD idea is one that helps others
- Building something that solves a real problem > building something cool
Insight: We could have built a game, a social app, or many other things. We chose to build something that helps people in pain. That made the hard parts worth it.
💡 About Building
#2: The Path Is Harder Than Expected, But Possible
- Turning an idea into reality is genuinely difficult
- Unexpected problems appear every day
- But with resilience, it's possible
- Pushing through is the difference between dreamers and builders
Insight: Day 4 was the hardest. We wanted to quit. We didn't. That made the difference.
💡 About Talent
#3: You Don't Need to Be Exceptionally Gifted
- One of us didn't know much about coding at the start
- Didn't stop us
- Good intentions + willingness to learn > perfect skills
- Simply taking action is already a great step forward
Insight: The barrier to entry is much lower than we thought. Anyone willing to try can build something meaningful.
💡 About Teamwork
#4: Collaboration Multiplies Capability
- Two people doing different things = more than twice as much gets done
- Communication matters more than coding skill
- Supporting each other through difficult moments is crucial
- Your team can accomplish what you never could alone
💡 About Purpose
#5: Purpose Sustains You Through Difficulty
- Work is hard when you're chasing metrics
- Work is energizing when you're helping people
- Knowing someone could benefit from what you build changes everything
- Purpose > profit, at least for meaningful work
🚀 What's Next for Mentta
Our Vision:
We want to keep building Mentta and reach as many people as possible.
Our goal is clear:
✨ Improve the experience — Make it even easier and more helpful to use 🌍 Expand across platforms — Web, tablet, better mobile experience 👨⚕️ Involve real psychologists — Connect AI support with professional help 💼 Become sustainable — Build a real company that can survive long-term ♿ Stay accessible — Always free for those who need it most
The Roadmap:
PHASE 1: POLISH & EXPAND
├─ Mobile app version 2.0
├─ Add therapist connection feature
├─ Expand language support (5+ languages)
└─ Reach 10,000 users
PHASE 2: PROFESSIONALIZATION
├─ Partner with licensed therapists
├─ Clinical validation of outcomes
├─ Enterprise (school/company) version
└─ Reach 100,000 users
PHASE 3: SCALE GLOBALLY
├─ Web platform
├─ Wearable integration
├─ Preventive features (not just crisis)
└─ Reach 1M+ users
Our Promise:
Because when someone needs support, Mentta is there. Mentta doesn't shut down. Mentta doesn't judge. Mentta is there.
That's our commitment. When crisis hits at 3 AM and there's no therapist available, Mentta will be there.
📊 Key Metrics
| Metric | Status |
|---|---|
| Development Time | 7 days ✅ |
| Languages Supported | 2 (Spanish + English) ✅ |
| Features Implemented | 8+ core features ✅ |
| Team Size | 2 focused developers ✅ |
| Code Quality | Production-ready ✅ |
| User Testing | Feedback implemented ✅ |
| Video Demo | 60-second professional version ✅ |
🎯 Conclusion
Mentta is proof that:
- Good ideas come from real problems — We saw people suffering, so we built a solution
- Small teams can ship fast — 2 people in 7 days delivered a working product
- You don't need to be perfect to start — Learning on the job is okay
- Purpose matters — Building to help people sustains you through difficulty
- The barrier to entry is lower than you think — Anyone willing to try can build something meaningful
We're just getting started.
Join us in making mental health support accessible to everyone, everywhere, always.
📱 Connect With Us
- Try Mentta: mentta.app
- Follow Us: @mentaapp
- Feedback: support@mentta.app
- Join Us: We're hiring developers, designers, and people who care
🙏 Final Words
Thank you for reading our story.
We built Mentta because we believe mental health support is a human right, not a luxury.
If you're reading this and struggling: You're not alone. You're not weak. Reaching out is brave. Mentta is here.
If you're reading this and want to help: We need you. Join us in making mental health accessible to everyone.
🧠 Mentta: Because support shouldn't wait. Help shouldn't be scarce. Hope shouldn't be expensive.
💙 Thank you for believing in Mentta.
Built With
- docker
- google-gemini
- google-maps
- html
- javascript
- mysql
- php
- railway
- react
- tailwind
- three.js
- typescript
Log in or sign up for Devpost to join the conversation.