EcoTrack

• 

Inspiration

Every city struggles with one common issue: waste mismanagement. People see garbage on the streets but they don’t know where to report it. Authorities want to act, but they don’t get timely information. Cleaning staff wants clear instructions, but they receive scattered complaints.

EcoTrack was inspired by one simple thought:

“What if citizens, authorities, and cleaning staff could stay connected in a single real-time system?”

This idea came from everyday frustrations — dirty streets, delayed clean-up, and no proper reporting mechanism. EcoTrack was created to solve this gap in the simplest, most accessible way.

What it does

EcoTrack creates a complete waste-reporting ecosystem, connecting all roles:

👤 Citizens

Report waste with description + photo + location

Track the status of their reports in real-time (Pending → In-Progress → Resolved)

🧑‍💼 Authorities

Approve new staff registrations

View all incoming reports

Assign reports to specific staff members

👷 Cleaning Staff

View tasks assigned to them

Mark tasks as “In-Progress” or “Resolved”

Work in a smart, structured workflow

🛡️ System Admin

Approve new authority accounts

Manage high-level access

Maintain system-wide security

EcoTrack ensures speed, transparency, and accountability in waste management.

How we built it

EcoTrack was built using:

• Next.js (App Router)
• React + Tailwind CSS
• Firebase Authentication
• Firestore Database
• Firebase Storage (optional feature)

• AI-assisted development using ChatGPT

• The project was developed in rapid iterations:

• Auth System — login, register, logout

• Role-based Routing — citizen, staff, authority, admin

• Waste Reporting Engine — Firestore-based CRUD

• Approval & Assignment System

• Dashboards for each role

• UI/UX Enhancements

Most problems (routing issues, Firestore bugs, auth logic, etc.) were debugged by using reasoning + AI support. This improved development speed while keeping logic clean and scalable.

Challenges we ran into

🚧 1. Firebase & Firestore Sync Issues

We faced multiple failures when the user collection was accidentally deleted and had to rebuild from scratch.

⚠️ 2. Role-Based Redirection Bugs

Users were redirected incorrectly (citizen instead of staff/authority) and required a complete redesign of the authentication flow.

🔁 3. Debugging Under Time Pressure

We had only a few days. Constant routing errors, storage limitations, and hydration issues in Next.js created unavoidable delays.

❌ 4. Deployment Issues

Some features caused Next.js build errors, which made us decide not to deploy and instead present the project as a working local prototype.

But in the end, every challenge strengthened the system and the development skills behind it.

Accomplishments that we're proud of

• Built a fully functional multi-role waste reporting system
• Clean UI and smooth user experience
• Clear role-based authentication
• A working workflow: Citizen → Authority → Staff → Resolution
• Completed the project in a very short time
• Strong example of AI + Human collaboration building a full-stack SaaS

What we learned

• Handling complex role-based systems
• Managing Firestore rules & database structure
• Debugging Next.js hydration, routing, and CSR issues
• Working under real hackathon pressure
• How powerful and efficient AI-assisted development can be
• Importance of keeping a clean architecture so debugging becomes easier

What's next for EcoTrack

This is just Version 1. Future improvements include:

🗺️ 1. Google Maps Integration

Smart location tagging and exact pinning.

🤖 2. AI Insights

Suggesting staff assignment, detecting waste type from images, smart routing, etc.

📊 3. Analytics Dashboard

City-level analytics for authorities.

📱 4. Mobile App Version

A lightweight React Native app for faster citizen reporting.

🏙️ 5. Hyperlocal Add-ons

Integration with hyperlocal businesses and municipal departments.

EcoTrack has the potential to grow into a full-fledged civic management platform.

Built With

• javascript
• nextjs
• tailwind