Team 7 — Pomodoro Timer First Brainstorm

Meeting Details

Date: April 10, 2025

Time: 4:00 PM – 5:30 PM

Location: CSE Building Room 2154, UC San Diego

Meeting Type: First Brainstorm Session

Attendance

Members Present

Members Absent

Agenda

  1. Review project requirements
  2. Discuss attendance and team roles
  3. Address old business from previous class meetings
  4. Brainstorm core features for the Pomodoro Timer
  5. Identify stretch goals
  6. Decide on the tech stack
  7. Assign action items
  8. Open floor for miscellaneous questions

Old Business

Priya reminded the team that the team contract was submitted last week. All members have signed it and agreed to the communication norms. The team will continue using Discord as the primary communication channel and GitHub for version control.

Marcus confirmed that the shared GitHub repository has been created and all members have been added as collaborators.

New Business

Core Features

The team agreed on the following core features for the Pomodoro Timer application:

  • A configurable timer with default 25-minute work and 5-minute break intervals
  • Start, pause, and reset controls
  • Visual progress indicator showing time remaining
  • Audio notification when a session ends
  • Session counter to track completed pomodoros

Stretch Goals

The following stretch goals were discussed. Click each item below for more details:

Task Labeling and History Log

Sofia proposed allowing users to label each pomodoro session with a task name. A history log would display past sessions with timestamps and task labels. This could be stored using localStorage so data persists between browser sessions. The team agreed this was feasible if time permits.

Statistics Dashboard

James suggested a statistics dashboard showing daily, weekly, and monthly productivity summaries with simple bar charts. Aiko noted that this depends on the history log feature being implemented first. The team flagged this as a lower-priority stretch goal.

Customizable Themes

Marcus brought up the idea of letting users pick from several color themes. This would involve toggling between predefined CSS classes. The team liked this idea for polishing the final product.

Tech Stack

After discussion, the team decided on the following technologies:

  • HTML5 and CSS3 for structure and styling
  • Vanilla JavaScript for timer logic and DOM manipulation
  • GitHub Pages for deployment
  • Jest for unit testing

Action Items

  1. Priya — Draft the project roadmap and milestones by April 14
  2. Marcus — Create wireframes for the main timer interface by April 14
  3. Sofia — Research localStorage API and draft data model by April 16
  4. James — Design mockups for desktop and mobile layouts by April 16
  5. Aiko — Set up the Jest testing framework in the repository by April 14
  6. Liam — Configure GitHub Actions CI pipeline when available by April 18

Miscellaneous Q&A

Q: Should we support mobile browsers?
A: Yes. Marcus will ensure the layout is responsive from the start.

Q: Do we need a backend server?
A: No. The app will be entirely client-side using localStorage for persistence.

Q: When is the next meeting?
A: Thursday, April 17, 2025 at 4:00 PM in the same room.

Media

Whiteboard Photo

Photo of the brainstorm whiteboard from today's meeting:

Whiteboard showing brainstorm notes with feature ideas, tech stack decisions, and a rough sketch of the Pomodoro Timer interface layout

Meeting Audio Recording

Audio recording of the full meeting:

Meeting Video Recording

Video recording of the meeting:

Feedback Form

Please share your feedback on this meeting:

Your Information



Meeting Feedback

How would you rate the meeting overall?




Which topics were useful? (select all that apply)