Skip to content

v0.1.0-alpha

Choose a tag to compare

@AIsJump AIsJump released this 31 Mar 21:00
· 155 commits to main since this release

Read README.md for instructions on how to build locally

Scrum Meetings

In our meeting on 3/28, we had an in-depth team discussion about the high-level architecture and functionality of our application. One of the key decisions we made was to use Express.js as the framework for our backend implementation. We also explored the initialization process of the backend, including setting up routes and preparing it to handle requests from the frontend. On the front-end side, we discussed the development of Manager Cards as an important upcoming feature. At that point, most of the foundational components related to the drinks section—such as individual drink items, categories, and add-ons—had been implemented. With those elements in place, we decided that after finishing the rest of drinks we would shift focus toward building out the Manager interface. Only building cards for the moment. We agreed that the card components for the Manager section would be our next priority. These cards would serve as the visual and functional building blocks for managing items or data from the backend. Initially, the cards would display basic information, but we planned to add more interactivity and functionality—such as inventory tables and order graphs—as the front-end development progressed.

In our 3/31, we primarily focused on getting our application up and running. With both the frontend and backend in place at a minimal level, we implemented a unified “start” script using npm-run-all. This allowed us to run both parts of the application concurrently, streamlining the development workflow and ensuring the front and back ends communicate effectively during startup. We also reviewed the current state of our Minimum Viable Product (MVP). On the frontend, we began developing key components for essential user flows, including the checkout and login pages. In addition, we started implementing the structure for browsing drink categories, where each category includes a set of individual drink items along with configurable add-Ons. On the backend, we moved away from hardcoded data by setting up dynamic communication between the frontend and a connected database. This allows drink data to be fetched from the backend in real-time, making the system more flexible and scalable as we continue development.

During our meeting on 4/2, we focused on reviewing the progress made across both the backend and frontend of the application. On the backend, we worked on developing API endpoints to allow seamless communication between the frontend and database, aiming for efficient and reusable data access throughout the app. This included setting up calls to dynamically fetch and manage drink data instead of relying on hardcoded values. On the frontend, we began implementing key UI components inspired by previous project work, such as the inventory table, order functionality, order history histogram, and the X and Y reports used for logging and financial tracking. We also made initial updates to the Settings page layout. As the frontend still relies heavily on backend support to be fully functional, we agreed that the upcoming focus would be on completing more of the backend and API development and to begin work on the Checkout Page to improve the core user experience.