Building strong relationships means showing up when it counts. Whether it is a birthday, a check-in after a job interview, or a quarterly coffee catch-up, remembering the "when" is just as important as the "who."
To help you stay on top of your network, we are introducing Reminders.
You can now set dedicated alerts for any of your contacts. Instead of cluttering your primary work calendar or relying on memory, your relationship follow-ups live exactly where your context is - right next to your notes.
How It Works
Each person in your network can now have up to 7 active reminders. When you create a reminder, you set a specific date, a time, and an optional note (up to 500 characters) to remind your future self exactly what you need to discuss.
From an interface perspective, it is a simple addition. But under the hood, we made some specific engineering choices to ensure your data remains accurate and future-proof.
┌──────────────────────────────────────────────────────────────────────┐
│ Client Application │
│ { "remind_date": "YYYY-MM-DD", "remind_time": "HH:MM", "note": "" } │
└──────────────────────────────────┬───────────────────────────────────┘
│ POST /reminders
▼
┌──────────────────────────────────────────────────────────────────────┐
│ Go API Server │
│ │
│ 1. Authenticate user request │
│ 2. Validate payload (Date/Time formats, Note length) │
│ 3. Execute Transaction: │
│ a. Lock person row (FOR UPDATE) to prevent race conditions │
│ b. Verify user has < 7 active reminders for this contact │
│ c. Insert into database │
└──────────────────────────────────┬───────────────────────────────────┘
│
▼
┌──────────────────────────────────────────────────────────────────────┐
│ PostgreSQL Database │
│ │
│ Table: reminders │
│ - remind_date (DATE) -> strictly preserves calendar day │
│ - remind_time (TIME) -> strictly preserves wall-clock time │
└──────────────────────────────────────────────────────────────────────┘Preparing for Google Calendar
This separation of Date and Time is not just about data integrity - it is the foundation for our next major feature.
By storing the user's intended date and time locally, we are perfectly positioned for our upcoming Google Calendar integration. When that ships, the backend will take your stored remind_date, your remind_time, and your account's current timezone preference, combining them dynamically to generate the precise RFC3339 format required by the Calendar API.
Reminders are live now. Go set up a coffee chat with an old friend!