Home
/

About

About

Why I built ComingUp Today

ComingUp Today started as a practical solution for my own household: a single shared view of what’s coming up for multiple people, across multiple calendars — without the constant “what’s on your schedule?” back-and-forth.

The core problem it’s meant to solve is miscommunication — the “I didn’t know you had something then” moment that leads to last-minute scrambling.

Hectic family whiteboard calendar

It started with one family

I have three kids, and our family schedule is layered and non-traditional. We needed an easy way for my wife and me — and eventually the whole family — to see the day, week, and month at a glance: school activities, appointments, reminders, routines, and the other moving parts that create daily friction when nobody has the full picture.

What began with our busy family grew into something useful for individuals and households more broadly. Calendars, lists, notes, contacts, and recipes can help with ordinary days as well as more involved family or caregiver coordination. A supported AI assistant is optional.

A shared screen in the kitchen

Household Display is an optional way to use ComingUp Today: a browser-capable screen in a central place that everyone can glance at. Ambient mode can rotate through available content; you do not need a dedicated display to use ComingUp.

The same shared schedule is available on a computer, tablet, or phone, at home and on the go. People can coordinate without shared editing access to their source calendars; events created in ComingUp remain editable where permissions allow.

Built by an experienced engineer

ComingUp Today is built by FE-Engineer, a software engineer with over 13 years of experience working on large-scale products and complex applications.

My background is primarily frontend, but I work full-stack and have helped build and launch high-traffic sites and production systems — including as a founding engineer at a startup. ComingUp Today is a founder-led, independent product shaped by daily real-world use.

If you're interested in the technical side of how it's built, you can find more work and writing on FE-Engineer.com and on YouTube.

Product principles

Clear boundaries for shared information

I want ComingUp to be useful without blurring the difference between seeing information and being allowed to change it:

  • Read-only imports: ComingUp displays Google and iCloud events you authorize, but does not modify those source calendars. Events created in ComingUp are editable where permissions allow.
  • Membership and visibility: access follows ComingUp organization membership and permissions, with controls for which imported calendars appear. ComingUp does not infer physical household boundaries; separate organizations remain separate.
  • Disconnect when needed: a successful disconnect removes stored connection credentials and stops future loading from that connection. Your source calendars remain with their provider.

Details are available in the Privacy Policy and Security pages.

Location data includes © OpenStreetMap contributors and other OpenCage data sources.

A deliberate limit

Important note about health data

ComingUp Today is not designed for storing or managing protected health information (PHI) and should not be used as a healthcare system. Please avoid adding sensitive medical details to event titles or notes.

Part of my story

Veteran-owned and operated

I served in the U.S. Air Force for six years and built ComingUp Today as an independent, founder-led product.

Feedback and feature requests

If you'd like to share feedback or request a feature, email support@comingup.today.

Try ComingUp in your everyday life