313SafeBeds

313SafeBeds shows real-time Detroit shelter availability with privacy codes, one-click provider updates, and admin transparency—making safety visible when it matters most

Comment

Inspiration:

I grew up in poverty, like many of my peers. At a young age, when my family needed a safe place to stay, my mom, my brother, and I lived in a shelter. That memory has never left me.

Recently, I called local organizations looking for available shelter beds. The response was the same each time: “No beds available.” That moment was a turning point — I knew I had to be the change I wanted to see.

What it does : 313SafeBeds is a real-time shelter availability platform built for Detroit.

Survivors: Can instantly see which shelters have open beds, submit private requests using unique codes (no names needed), and receive confirmation when accepted.
Providers: Can update bed counts with one click, review and accept requests, and manage placements.
Admins: Have tools for verifying shelters, tracking capacity snapshots, and reviewing audit logs for transparency.

In short: 313SafeBeds makes safety visible when it matters most.

How we built it:

I built the app with: JavaScript / TypeScript (generated via Lovable export) SQL (for Supabase database + policies) Frameworks & Libraries: React (frontend, via Lovable) Vite (build tool) TailwindCSS (styling, accessible design system) Platforms & Cloud Services: Lovable.dev (AI builder + hosting) Supabase (PostgreSQL database, Auth, API layer) Database: PostgreSQL (Supabase managed instance) Row Level Security (RLS) for privacy + role-based access APIs & Integrations: Resend (email notifications; Twilio optional for SMS) Future: HUD/HMIS APIs for compliance and scaling Other Tools: GitHub (code hosting + version control) Vercel/Netlify (optional deployment for frontend builds)

Challenges we ran into:

This project was not easy. Along the way, I encountered: Repeated system errors while developing in Lovable. Exhausted credits on paid plans, which forced me to problem-solve creatively. The steep learning curve of database security and role-based access.

But with perseverance and mentorship, I kept pushing. Each obstacle became proof that I could overcome adversity — not just in code, but in life.

Accomplishments that we're proud of?

I'm proud of overcoming my fear of failure, and I'm proud of overcoming all major system issues and successfully deploying my idea.

What we learned Through this journey,

I’ve learned that building solutions is not just about technology, but about resilience.

I discovered the importance of:

Giving myself grace during setbacks.
Embracing challenges as learning opportunities.
Leaning on mentors for guidance and encouragement.
Never giving up, no matter how many obstacles come my way.

What's next for 313SafeBeds?

313SafeBeds began as a hackathon project, but the mission is much bigger. The next steps are clear:

Pilot Launch in Detroit: Partner with local shelters to test live capacity updates and survivor request flows.

Community Feedback: Work directly with survivors and providers to refine the trauma-informed design.

Integration with HMIS APIs: Connect with HUD-compliant systems so shelters don’t have to duplicate work.

Scalable Infrastructure: Expand Supabase role-based access and optimize the mobile experience for families in crisis.

Funding & Partnerships: Secure city contracts, nonprofit collaborations, and grants for long-term sustainability.

Expansion: After Detroit, scale across Michigan and eventually nationwide.

My ultimate vision goes beyond technology. One day, I want to open my own family shelter — a place that combines the transparency of 313SafeBeds with real, physical beds for families who need safety and dignity.

The goal is simple: no family should ever be left in the dark about where they can sleep tonight.

Built With

Share this project:

Updates