HackStack

Project Info

bash

Devpost

Inspiration

bash was born out of a personal need. Like many students, I often found myself unsure about where to find exciting events near my college. This uncertainty was a common topic among my peers, and it sparked the idea to create an app that simplifies the process of discovering social gatherings and activities.

What it does

The goal is to help fellow students overcome the challenge of navigating the campus social scene and make the most of their college experience. The app allows users to enter their .edu email. Upon verification, students can view a collection of events happening on and near campus.

How we built it

Our group of 4 decided to split up into front and back end pairs. For the frontend development of our project, Ryan and Michael have leveraged the power of React Native to craft a dynamic and responsive user interface. Our primary screens include the Home screen, where users can effortlessly browse and access a curated list of upcoming events, and the Event Detail screen, which offers a comprehensive view of specific events. We're also implementing a Search screen, which empowers users to find events based on various criteria such as title and date. To ensure smooth navigation between these screens, we're utilizing React Navigation, ensuring an intuitive and seamless user experience. Additionally, we've chosen Redux for state management, ensuring data flows smoothly across the app, delivering a consistent and reliable experience. Lastly, we're committed to designing a responsive UI that adapts to different screen sizes, guaranteeing a visually appealing and user-friendly interface across various devices. For the backend, Neel and Daniel have built a robust foundation with a Node.js server, harnessed by the versatile Express framework. Our objective is to create a seamless and efficient backend system, facilitated through REST APIs that encompass all critical operations. These operations include fetching upcoming events, retrieving event details by their unique identifiers, and handling user registration and login functionalities through secure POST requests. Additionally, we've implemented GET and POST routes to manage user profiles and saved events, ensuring a personalized experience for our users. To guarantee the security and privacy of user data, we've incorporated a user authentication mechanism, requiring users to authenticate before accessing their profile-related APIs. Our backend infrastructure is designed to be both powerful and secure, underpinning the seamless functioning of our application.

Challenges we ran into

Since none of our team members had used Express.js and Node.js, backend development was a bit slow at first. Additionally, it took a lot of time to put together all individual components of our fullstack program.

Accomplishments we're proud of

At the beginning of the hackathon, our team spent a lot of time planning the entire project from ideation, design, and technical specs instead of jumping straight into coding the product, which is a common mistake many engineers make including ourselves in previous hackathons. This way, our team was able to be on the same page and better understand each others’ roles to collaborate smoothly.

What we learned

Above all, we learned how to communicate effectively and play to each of our strengths so that the project could be finished efficiently and effectively.

What's next

Currently, we’ve been focusing just on college students. We’d like to expand to a lot of other demographics, as everyone needs activities to do.

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
  • JavaScriptIn code
  • ReactIn code
  • ExpressClaimed
  • Node.jsClaimed

2 of 4 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

73 KB

Source files

22

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

0 stars