Healthy Bites
Nutrition and habits platform with three roles. Clients track goals and habits, nutritionists publish plans, and an admin manages users and billing.

- Role
- Technical lead and full-stack developer in a university team of five; sole author of the 2026 rebuild
- Period
- Aug 2024 — Dec 2024
- Status
- Completed
- Stack
- Java
- Spring Boot
- Angular
- Astro
- PostgreSQL
- PayPal
- Playwright
Healthy Bites is a university project that closed in 2024. I led a team of five and wrote most of the code. In November 2026 I went back to it on my own to modernize it, and rebuilt it as three deployable pieces: a Spring Boot API, an Angular web app and an Astro landing page. It is an academic and portfolio project, not a commercial service, so payments run in the PayPal sandbox.
How it works
- Clients set a weight goal, log weigh-ins and daily habits, follow meal plans, read content, join groups and subscribe to a paid tier.
- Nutritionists publish meal plans, content and rewards. They join by admin invitation only.
- Admins manage accounts, invitations, moderation and billing.
The backend is a modular monolith with eleven modules, such as identity, billing, nutrition, progress, rewards and community. Modules share only identifiers and talk through public interfaces or persisted events. Logging a habit publishes an event; the rewards module listens, advances the streak and unlocks the prize.

Engineering decisions
- Architecture checked by tests. Spring Modulith and ArchUnit tests fail the build when one module reaches into another. CI also fails if the OpenAPI contract or the module documentation drifts from the code.
- Sessions. A 15-minute access token kept in memory, plus a refresh token in an HttpOnly cookie that rotates on every use. Reusing an old refresh token revokes the session.
- Payments verified on the server. The API creates the PayPal order and, on capture, checks the owner, the amount and the currency. Capture is idempotent.
- A typed contract between repositories. The web app generates its API types from the backend’s OpenAPI file, and CI checks that they match.
- Accessibility as a gate. End-to-end tests run axe against WCAG 2.2 AA on every route, on desktop and mobile viewports.



Repositories
- API: Java 25, Spring Boot 4, PostgreSQL, Flyway.
- Web app: Angular 22, PrimeNG, Tailwind CSS, Playwright.
- Landing page: Astro, Tailwind CSS.