HackStack

Project Info

Ordo

Devpost

This project did not submit a demo video on Devpost.

Inspiration

One of the team members has 96% of their Google storage full. Where over 50% of that storage consists of just emails! This is solely due to one of our team members laziness of reading through an abundance of emails that are sent to her inbox daily where most of them are just spam and promotions. To amend this issue, we created a Google Chrome extension that uses the power of AI to analyze an email's content and user friendly interface to delete unwanted emails.

What it does

Ordo is a Google Chrome extension that utilizes Google's ecosystem to organize user's emails and delete emails based on chosen filters. Users open a pop up and are able to choose between deleting and organizing emails. To delete emails, users can choose filters to specify what kind of email they want to delete. To organize emails, an AI analyzes groups of emails and finds similarity between them creating a label to organize them. Users are able to accept and decline the labels generated by the AI.

How we built it

. Figma: Creating the Wireframe Mock Ups Firebase Functions: Creating HTTPs Requests / API Calls Firestore: Database to hold emails in the system and pending deleted/organized data Vite/React: Frontend Chakra UI: Frontend Components Groq: AI to analyze email content. Gmail API: API to handle changes to email.

Challenges we ran into

. Understanding the Gmail API and coming up with an idea. Dependency issues due to manifest and crxjs from Vite being outdated. Issues with integration of both the backend and the frontend. Styling issues due to predefined chrome extension template behavior.

Accomplishments we're proud of

. Casey: I am proud we showed up. Justin: I am proud I was able to develop a responsive and feasible front-end for a chrome extension.

What we learned

. Learned how to make a google chrome extension. Learned to plan out the architecture and map out the workflow of the application. Learned to plan out components for frontend so individual files don't get too congested. Make better design decisions revolving around states to reduce the amount of states that need to be managed.

What's next

. Scale up to have quicker processing for users with a large inbox. Add animations to UI to make user experience better and more responsive.

Analysis

Compare with all teams

View

Metric

Figures cover GitHub contributors during the hackathon window. A co-authored commit counts in full for each author, so per-member totals add up to more than the whole-team figures.

Technology

Found in codeClaimed only
  • CSSIn code
  • HTMLIn code
  • JavaScriptIn code
  • ReactIn code
  • Tailwind CSSIn code
  • TypeScriptIn code
  • FirebaseClaimed
  • PythonClaimed

6 of 8 appear in the indexed code. 2 claimed on Devpost could not be matched to code, which may simply mean the tool leaves no trace in the repository.

AI coding agents

No AI coding agent signals were found in this repository.

Detected from committed agent config files and commit authorship. Absence of a signal is not proof an agent was unused.

Codebase size

Source size

69 KB

Source files

36

Counts recognized source files only; vendored directories, binaries and lockfiles are excluded, so this is smaller than the repository on disk.

0 stars