a1mb0t38/Med-Track

Med-Track is a useful and thoughtful project that helps users manage medicine schedules and lets caregivers view progress from a separate dashboard. The repository includes patient and caregiver roles, dose tracking, refill alerts, adherence charts, invitations, settings, authentication, and browser notifications. These features work together around a clear real-world problem, which gives the project a strong purpose.

The code is organized well for a growing Next.js application. Pages are grouped by role and feature, while larger parts of the interface are placed in separate components. The split between client-side and server-side API helpers is also a smart choice. The README explains why this split matters, which can help future contributors avoid common Next.js errors. The use of TypeScript, a lock file, reusable components, and a live Vercel deployment are all positive signs.

The README is detailed and does a good job of explaining how patients and caregivers use the app. However, the setup steps do not fully match the repository. They tell users to enter a frontend folder, but the frontend files already appear at the repository root. The guide also refers to a separate backend README that is not included here. Adding a direct link to the backend repository, an .env.example file, and one complete local setup guide would make the project much easier to run.

Testing should be the next major focus. There are currently no automated tests or GitHub Actions workflows in the repository. Medication schedules, dose status changes, caregiver permissions, date handling, and authentication are important areas that deserve reliable test coverage. A basic CI workflow could run the existing lint and build commands on every pull request. Unit tests could then cover schedule calculations and API helpers, while browser tests could check signup, login, dose tracking, and caregiver access.

Notifications also deserve extra attention. The current reminder system uses browser timers, so reminders may not run after the page is closed, refreshed, or placed to sleep by the device. The README should explain this limit clearly. A more reliable future version could schedule reminders through the backend and use real web push notifications. Since the app handles health-related information, the project should also document its privacy model, data retention rules, security choices, and intended limits. It should avoid suggesting that reminders are guaranteed until that behavior has been fully tested.

Finally, adding a license, contribution guide, issue templates, screenshots, and a short architecture diagram would make the repository feel more complete. Overall, Med-Track has a strong idea, a clear interface, and a good starting structure. With a complete setup path, automated tests, stronger notification delivery, and clear privacy documentation, it could become a much more dependable and welcoming project.