Hi guys!
I've been independently building an open-source project called PawHaven over the past two years.
It's an animal rescue platform designed to connect volunteers, animal shelters, and people interested in adopting stray animals.
I built the project from scratch, covering the frontend, backend, system architecture, and deployment.
Tech Stack:
- Frontend: React, TypeScript
- Backend: Node.js, NestJS
- Architecture: API Gateway + 3 independently deployed services
- Infrastructure: Vercel, Cloudflare
I'm looking for honest and constructive feedback from experienced developers.
I'd particularly appreciate your thoughts on:
- Overall system architecture and service boundaries.
- Code quality and project structure.
- Backend API design and service communication.
- Security, scalability, and maintainability.
- Anything you think could be improved or redesigned.
I'm open to critical feedback. The goal is to identify weaknesses and make the project better, rather than simply showcase what I've built.
Live: https://pawhaven.work
GitHub: https://github.com/aoda-zhang/PawHaven-FullStack-React-NodeJS
I'd really appreciate it if you could take a look and share your thoughts. Thanks!
Top comments (3)
I just created an account, and the first thing i noticed is that there is no solid reason to make someone create an account, at least for now... Even the feature to record a stray animal isn't a solid use-case for obtaining personal data from user; The one rule i use to know if my app really needs authentication is if my app has personalised info the user would like to visit some other time to access
But great project regardless, and solid UI (it's not the regular ai slop that most agents create nowadays) - it's actually unique and interesting
Side note: fell in love with the loading animation...
Thanks a lot for taking the time to explore PawHaven and share such detailed feedback!
You make a really good point about authentication. I agree that requiring users to create an account before they can access the core features may introduce unnecessary friction, especially for first-time visitors. I'll definitely reconsider the current approach and explore whether some features could be accessible without registration.
I also appreciate your point about personalized information. That's a useful way to think about whether authentication is actually necessary.
And thanks for the kind words about the UI! I'm especially happy you liked the loading animation. I spent quite some time working on the overall design and user experience, so it's great to hear that it stood out.
Really appreciate your feedback!
Anytime for open source 🔥