REMINEXA
Personal reminders with scheduled notifications, history and email delivery.
V1 pilotAccess requires a verified account and an invitation. The website opens the sign-in screen.
The problem
Tasks, deadlines and administrative commitments become scattered across notes and calendars. A reminder needs context and a record of what happened to its notification.
Every screen tells a story.
Explore the project, screenshot by screenshot. From the big picture to the details that make a difference.
Overview
What it enables
Reminders
Organization of personal commitments and their dates.
Email notifications
Daily processing and HTTPS integration with Resend.
History and attachments
Reminder context, tracking and private files.
Decisions behind the solution.
- React · SPA
- Spring Boot · API
- PostgreSQL · Neon
- Cloudflare → Resend
Idempotent processing
Processing is designed to avoid repeating work when the job runs again.
External scheduler
A Cloudflare Worker runs the daily process without keeping the service permanently awake.
Private files
Attachments have access controls, type validation and size limits.
What I solved with this project.
- Bring commitments, context and files together in personal reminders.
- Connect daily scheduling to notification processing and email integration.
- Review attempt history and manage reminders while preserving their context.
How I support the work.
The Verify REMINEXA workflow configures frontend and backend builds and tests. The repository includes Worker configuration and V1 operational guidance.
Architecture
Components, data and integration.
Material to be addedTechnical decisions
Alternatives and implementation criteria.
Material to be addedTests and results
Journey validation and evidence.
Material to be added