SMF·MORGEN
Can a prompt replace Morgen?
Tasks & to-dos — personal tasks, routines and daily planning
Exhibit tracking slip
Verdict
Aggregating two or three calendar accounts you already have into one unified weekly view, alongside a simple task list, is a real weekend-to-week build using each provider's own API. What doesn't survive: Morgen's polish across many calendar and task-app integrations at once, and years of edge-case handling for how different providers represent recurring events and timezones slightly differently.
Exhibit A — The prompt
Received on31.07.2026Build a unified calendar view aggregating two calendar accounts you actually use — for a personal project, two, such as a work Google account and a personal one, is a realistic and honest scope; Morgen's support for many providers at once is real, larger integration work. Use Next.js/TypeScript with the Google Calendar API (OAuth) for each connected account — if one of your accounts is Outlook or iCloud, that's a separate API integration with its own quirks, and adding a second provider type roughly doubles the integration work, which is worth being upfront about. Merge events from both connected accounts into one unified weekly view, color-coded by source account, with overlapping-event handling that shows both clearly rather than hiding one. Maintain a simple task list alongside the calendar, title, due date, done state, stored locally, without syncing to an external task app. Handle recurring events by expanding each provider's recurrence rule into individual instances for display — this is the specific area where providers diverge in representation, so test it carefully. Do not build support for more than two calendar accounts, task-app integrations beyond the built-in list, or native mobile apps — those are out of scope. Needs an OAuth app registration per calendar provider you connect; no other external service required.
Opening prefills the prompt — press enter to run it.
Exhibit B — What you lose
- B.1 polish across many calendar and task-app integrations at once
- B.2 years of provider-specific recurring-event and timezone edge cases
- B.3 cross-platform native app polish
- B.4 team scheduling features
Prior art
Exhibit C — Why people still pay: cross-device reliability and workflow polish
Merging two calendars once is a weekend; correctly handling how Google, Outlook, and iCloud each represent recurring events and timezones slightly differently, reliably, for years, is the accumulated integration work.
Questions
How many calendars can it connect?
Two, by design — Morgen's support for many providers and accounts at once is real, larger integration work each additional provider type roughly doubles.
Does it integrate with Todoist or Asana for tasks?
No — this build keeps its own simple local task list rather than syncing with external task apps, which is a real feature gap compared to Morgen.
Will recurring events show up correctly from both calendars?
That's the trickiest part to get right, since providers represent recurrence slightly differently — test this specifically rather than assuming it just works.
What does it cost to run?
Minimal hosting plus each calendar API's free tier — typically a few dollars a month or less.
Related tools
Receipt