GDGoC Task Management App

GDGoC teams coordinate events, learning programs, and internal work across many owners. Members need to see who owns a task and when the team expects delivery without reading several chat threads.

Problem

Task ownership, deadlines, and status lose context when teams spread them across chat and documents. A list can show tasks, though it gives a weak view of timing and workload across a month.

Role and scope

I worked on the product as a full-stack contributor. We did not keep a contribution log, team roster, or operating period, so I avoid a sole-builder or adoption claim.

Process and decisions

The app places tasks on a shared calendar. Members can filter their work, while team views show owners and status. Firebase sends changes to connected users after an update.

Drag-and-drop rescheduling keeps the date change inside the calendar context. The interface still needs history and permission controls for accountable operations.

Working flow

The build covers calendar visualization, owner filtering, task reassignment, drag-and-drop dates, and Firebase updates across connected sessions.

I did not retain active-user counts, task volume, delivery changes, or usability results. The former domain no longer responds.

Limits

I would need the codebase, release notes, role rules, and a team pilot before presenting the app as more than a working demonstration.