Inspiration
Social media connects the world—but often at the cost of our inner peace. In an age where likes and followers feel more important than authenticity, worry, anxiety, and depression have become widespread. Many suffer silently, trapped between public personas and private pain.
As someone who has worked closely with individuals navigating mental health struggles, I’ve seen how powerful even the smallest gesture of support can be. While I may not experience these challenges myself, I believe in creating tools that help others feel heard, validated, and less alone.
I first envisaged WorryBox about 20 years ago. I have since then had no time to put it together.
What it does
WorryBox is a social platform that allows users to:
- Share their worries anonymously or publicly.
- See how many others are dealing with similar concerns so they know they are not alone.
- Receive tips and encouragement tailored to each worry.
- Track their emotional journey over time in a private dashboard.
- Uses AI to moderate comments to keep the platform troll-free.
- Share their worries and thoughts, blog their reasons, and track which worries they have overcome.
It’s part community, part emotional toolkit, and 100% judgment-free.
How we built it
As a seasoned and experienced developer, I have generally used AI as a bug-hunting or log-reading tool. However, I wanted to experiment and see just how far Kiro could go. I gave it full control and tried not to interfere.
I began by describing the platform I have concidered building for many years. I laid out the features, requirements as I would to a team. I let Kiro build the design and implementation docs it needed and after a review, let Kiro get to work.
I have endevoured to do as little of the actual coding myself as possible for this. Keeping my role entirely as product manager and providing the guidance and prompts Kiro needs. I have been surprised, disappointed and confused along the way. But Kiro is doing a good job.
Challenges we ran into
It was important in my original plan to avoid the possibility of the platform causing more harm. There are many out there who feed of the misery of others, and seem to enjoy causing deperession rather than trying to fix it. Therefore I was worried that some may use the platform purely to troll those who are looking for help, and others might use the platform to post ridiculous and misleading posts. For this reason, I intended for comments and posts to pass through AI to check for harmful intentions and flag them for human review.
The second challenge is, and continues to be, money for hosting. By the end of the hackathon I hope to have the platform running somewhere were it can be tested.
Accomplishments that we're proud of
- A working prototype with a friendly brand identity
- A clean UX that invites introspection without pressure
- A real-time worry clustering system that highlights common themes
What we learned
- Some people need help, but actively refuse it. Prefering to keep themselves miserable as it's what they know.
- Kiro is an excellent tool that could go very far.
- Most developers might find themselves mostly just checking code generated by AI rather than writing code themselves. But also getting more free time to do other things.
What's next for WorryBox
- Partner with mental health professionals for optional guidance
- Explore mobile versions and local language support
- Launch a public beta to grow the community organically
Built With
- anxiety
- axios
- bcryptjs
- connect
- cors
- date-fns
- eslint
- express-rate-limit
- express-validator
- express.js
- helmet
- javascript
- jest
- jwt
- lucide-react
- node-cron
- node.js
- nodemailer
- openai-api
- postgresql
- prettier
- prisma
- react
- react-hook-form
- react-hot-toast
- sql
- stripe
- supertest
- tailwind-css
- ts-jest
- typescript
- validated
- vite
- worry
- zod
Log in or sign up for Devpost to join the conversation.