- React JS
- Express JS
- MongoDB
- Firebase
Paws & Tails
Paws & Tails is a pet adoption and animal-donation platform, not simply a pet listing website. Its strongest case-study story is the combination of pet adoption workflows, user-managed listings, donation campaigns, payment processing, and role-based administration.
- ROLE
- Fullstack Developer
- DURATION
- 1 Months
- PLATFORM
- Web app

01 — Context & Problem
Paws & Tails is a full-stack pet adoption and donation platform designed to connect people interested in adopting pets with opportunities to support animals in need.
The platform brings several related activities into one application. Visitors can discover available pets, search and filter listings, and explore individual pet information. Registered users can contribute their own pet listings, submit adoption requests, create donation campaigns, and review their personal activity.
The platform also includes an administrative workspace for managing users, pet listings, and donation campaigns.
The main challenge was connecting these different workflows into a consistent application, where public discovery, authenticated user activity, administrative permissions, and donation records work together.
02 — Architecture
The application follows a separate frontend and backend architecture.
The frontend is built with React and Vite, using React Router for navigation and TanStack Query for server-state management. Firebase Authentication handles user sign-in, while Axios provides communication with the backend API. The interface combines Tailwind CSS and Material UI, with React Hook Form supporting form workflows.
The backend uses Node.js and Express to expose REST API endpoints. MongoDB stores application data across five collections: users, pets, adoption requests, donation campaigns, and payments. The MongoDB native driver is used for database operations.
Authentication is supported through Firebase on the client and JWT-based authorization on the API. The backend includes middleware for token verification and administrative role checks.
Stripe is integrated for card-payment processing. The application creates payment intents through the backend and stores donation payment records alongside campaign totals.
The frontend is deployed on Netlify. The backend repository includes Vercel deployment configuration.
03 — Engineering Decisions
DECISION
Separating the frontend and backend
Keeping the React application separate from the Express API established a clear boundary between the user interface and server-side data operations
DECISION
Using MongoDB for application data
The platform manages different kinds of records, including users, pet listings, adoption requests, campaigns, and payments
DECISION
Integrating Stripe for donations
Donation payments use Stripe Payment Intents, allowing the application to initiate card payments through a dedicated payment flow. Payment records are stored in MongoDB, and campaign donation totals are updated as payments are recorded.
05 — Outcomes
06 — Trade-offs & Reflection
Building the platform highlighted the importance of keeping related records consistent. Adoption requests, pet status, payment records, and campaign totals represent connected pieces of application state. Updating them independently can introduce inconsistencies if an operation fails partway through.
The implementation also demonstrates why authentication and authorization must be enforced at the API boundary. Frontend route protection alone cannot guarantee that a user is permitted to modify a particular resource.
A future iteration would benefit from stronger ownership checks across write operations, server-side validation of payment amounts, verified payment-completion handling, and transactional updates for related records. A more structured backend organization would also make the growing set of API operations easier to maintain.
The project represents an important step in developing practical full-stack skills: moving beyond individual pages and forms to building an application where users, data, permissions, and external services interact.
