Inspiration:

This shopping website was inspired by our observations of common online purchasing issues and our desire to build a simpler, faster, and more user-friendly platform while strengthening our web development and practical design skills.

How we built it:

We have used Visual Studio Code and Vercel for hosting the website.

Challenges we ran into:

We encountered a number of technical problems, particularly when features clashed or the code didn't function as intended. Another difficulty was managing time since it took self-control to balance project deadlines. Debugging complicated issues frequently took longer than anticipated, putting our tolerance and problem-solving abilities to the test.

Accomplishments that we're proud of:

We successfully finished fully functional projects from the ground up and witnessed our concepts become tangible results. Significant accomplishments included enhancing the quality of our code, creating more aesthetically pleasing interfaces, and working well as a team. Above all, we maintained our consistency and finished the tasks we began.

What we learned:

We discovered how to logically overcome setbacks and divide complex issues into smaller, more doable tasks. Planning, cooperation, and communication turned out to be just as crucial as technical expertise. All things considered, this experience gave us confidence, flexibility, and resilience when working on actual projects. Additionally, we now know how to code deeply using languages like JSON.

What's next for EcoMart

Add sustainability analytics, real-time notifications, and Stripe payments

Introduce multi-language support, blockchain-based carbon tracking, and social features

Make EcoTask and EcoMart smarter, more interactive, and more effective in promoting sustainability

Built With

Share this project:

Updates

posted an update

The platform has two ways for admins to log in. This means that if one login page is not working or it is being updated or there is a problem with it admins can still get into the system using the login page. This way the work can keep going without any stops. Both login pages take admins to the admin dashboard. The admins have the permissions no matter which login page they use. The admin dashboard is the same, for both logins. This setup also helps with: •Load handling during high traffic •Testing UI or security updates without blocking access •What if the company needs to split up jobs in the future will the system be able to handle that I mean the scalability of the system if roles need to be separated later like if the jobs become too big for one person to handle the future scalability of the system to separate these roles. So even though both logins do the same thing today, the structure is future-ready and improves system reliability.

Log in or sign up for Devpost to join the conversation.