Most couples manage shared appointments through screenshots and Apple Messages. Composed lets you invite your partner to a single event with one tap, generates an RSVP link via the share-event edge function, and surfaces the response inside both Composed and Apple Calendar. Apple Calendar family sharing and Google Calendar shared calendars both work for couples on iPhone, but neither generates AI prep tasks or the leave-by alerts that keep one partner from forgetting the school pickup.
The honest pattern across every parent and partnered household we’ve watched plan: nobody is missing the event itself. They’re missing the preparation — the mouthguard, the insurance card, the leave-by-3:20 because traffic. A shared calendar that only shows time and place still leaves one person doing all the cognitive work. The fix is sharing the prep, not just the appointment.
This guide covers the three real options for sharing a calendar with your partner on iPhone — Apple Calendar family sharing, Google Calendar shared calendars, and Composed’s shared events with RSVP — and which one fits which kind of coordination.
How do you share a calendar with your partner on iPhone?
There are three working ways to share calendars with a partner on iPhone in 2026: Apple Calendar family sharing through iCloud, Google Calendar shared calendars via Google Workspace or a personal Google account, and Composed’s per-event sharing through the share-event edge function. Apple Calendar is the simplest if both partners use iPhones; Google Calendar is the default if one of you is on Android or uses Google Workspace at work; Composed sits on top of either as the preparation layer with RSVP-by-link.
Apple Calendar family sharing is built into iCloud. Set up Family Sharing in iOS Settings, add your partner, then create a shared calendar (in the Calendar app: Calendars → Add Calendar → Add Shared Calendar). Both iPhones see every event added to that calendar, with editing permissions configurable per person. The setup takes about three minutes once Family Sharing is in place.
Google Calendar shared calendars work the same way but through Google’s web app or the Google Calendar iOS app. Create a new calendar, share it with your partner’s Google account, set their permission level (See only / Make changes / Manage sharing). The Google calendar shows up automatically in the iPhone’s Calendar app once added to Settings → Calendar → Accounts.
Composed sits at a different layer. Instead of sharing an entire calendar with everything in it, Composed shares one event at a time via the share-event edge function — you tap Share on a single event, invite your partner by username search, text, or email, and they get an RSVP link they can respond to without installing the app. The organizer sees the response inside Composed; the event also lands in your partner’s Apple Calendar if they tap “Add to Calendar” on the RSVP page.
What is the difference between event sharing and calendar sharing?
Calendar sharing puts an entire calendar in both partners’ hands, with every event automatically visible to both. Event sharing puts one event in one place, with an explicit RSVP. The difference matters: a shared calendar is for the ongoing rhythm (school dropoffs, recurring date nights, vacation week); a shared event is for the one-off coordination (“Can you come to this thing on Saturday?”).
Most couples need both. The school pickups, the kids’ soccer practices, the recurring family dinners — those belong on a shared Apple Calendar or Google Calendar, where both partners passively see them. The one-off — a friend’s birthday dinner, a doctor’s appointment one partner wants the other to drive to, a school conference — works better as a per-event invitation with an explicit yes/no response.
Apple Calendar family sharing and Google Calendar shared calendars handle the first case well and the second case badly. They have no real RSVP layer — your partner sees the event, but you don’t see whether they’ve actually committed to attending. Most couples paper over this with iMessage (“are you coming Saturday?”), which is exactly the group-chat coordination problem shared events without the group chat chaos covers in depth.
Composed’s shared events solve the second case explicitly. The RSVP options are Going / Maybe / Not for me, the response is timestamped, and the organizer sees every guest’s status in one screen. The notify-event-update edge function pushes an update notification to every guest if you change the time, location, or details — no manual “actually, it’s 7pm now” group text required.
Can shared events have AI prep tasks?
Yes — and this is the single biggest difference between Composed and every other shared-calendar option on iPhone. When you create a shared event in Composed, the generate-checklist edge function produces 3-5 AI prep tasks for the event automatically, the same way it does for any solo event. The organizer sees the prep tasks; the guest sees them on the RSVP page if they tap to view event details.
Apple Calendar family sharing does not generate prep tasks. Google Calendar does not generate prep tasks. Cozi, the most-named “family calendar” app on iPhone, does not generate prep tasks. The shared layer in those apps gives you the appointment; it doesn’t give you the preparation. That gap is the entire reason one partner ends up doing all the mental work — they’re holding the prep list in their head while the calendar shows everyone the same blank event.
A concrete example: parent A creates a shared event “Lily’s dentist Thursday 3pm” and invites parent B. Composed’s prep checklist generates: “Bring insurance card,” “Bring Lily’s medical history form,” “Leave by 2:30 — typical drive 18 minutes plus 10-minute buffer,” “Confirm Lily ate before noon (post-cavity rule).” Parent B accepts the RSVP and sees all four prep items. If parent B is the one driving Lily to the appointment, they have everything parent A would have brought, in their hand, on the RSVP page.
This is what the composed-product-truth.md calls the preparation layer — Composed doesn’t replace Apple Calendar or Google Calendar; it sits on top and handles what they were never designed to do. For the deeper explanation, see what is an AI prep checklist.
How does Composed’s RSVP for couples actually work?
Composed’s shared events flow runs through four Supabase edge functions: share-event (creates the invite + RSVP link), public-rsvp (lets the guest respond without installing the app), notify-event-update (pushes changes to every guest), and cancel-shared-event (cleanup when the event is canceled). The whole flow is designed so the guest never has to download Composed to participate — which removes the single biggest friction point in every other shared-calendar app.
Step by step: the organizer creates an event in Composed, taps the Share button, and chooses how to invite — by username search (if both partners have Composed installed), by text message (sends a shareable link via iMessage), or by email (sends an RSVP link to the partner’s inbox). The share-event function generates a public URL with a token-based auth so only invited guests can access the event details.
The guest taps the link. They see the event details on a clean web page: title, date, time, location, the host’s name, and the RSVP buttons (Going / Maybe / Not for me). They choose a response, which writes back to the organizer’s Composed instance through the public-rsvp POST endpoint. The organizer sees the response in real time on the event detail page.
If the guest also has Composed installed, the event is added to their Composed library automatically once they tap Going. If they don’t have Composed, they can tap “Add to Apple Calendar” and download a .ics file that imports the event with full details — title, time, location, description, and a link back to the Composed event page in case they want the prep tasks later.
The organizer can see who responded, when, and with which status. If the organizer changes the event — a new time, a different location, a canceled brunch — Composed fires the notify-event-update edge function and pushes the update to every invited guest’s RSVP page. No “actually, it’s 7 now” iMessage needed.
Can both partners get the leave-by alert?
When a shared event has a location, Composed’s departure tracking runs independently for the organizer and for any guest who’s accepted the invite and also installed Composed. Each partner gets a leave-by alert calculated from their own current location using Apple MapKit and Google Maps — so the partner driving from the office and the partner driving from home both get the right departure time, not the same one.
This is the layer Apple Calendar and Google Calendar can’t reach. Apple Calendar’s “Time to Leave” notification is roughly accurate for one location at a time, configured per-account; it doesn’t differentiate between two partners on the same event. Google Calendar has no built-in departure logic at all on iPhone — it relies on you setting a manual reminder time, which is wrong the moment traffic shifts.
Composed’s LeaveByCalculator includes the right buffers automatically. Drive-time plus a 10-minute generic buffer for a normal event. Drive-time plus a 120-minute airport buffer for a domestic flight. Drive-time plus 180 minutes for an international flight. The buffer math is built directly into the calculator so neither partner ends up the one telling the other “I think we should leave a little earlier” guessing on the fly.
For the underlying mechanic, see what is a leave-by alert — and departure time apps: how to always leave on time covers the broader pattern.
The three-layer reminder model also runs per-partner. The awareness ping (“Lily’s dentist Thursday — three days out”) fires once for each partner. The action nudge (“Leave by 2:30 — 22 minutes including drive plus buffer”) fires once for each partner from their own location. Composed suppresses the action layer when readiness score crosses 95%, so if you’ve checked off all the prep tasks, the nudges stop. See three-layer reminders for how the model is built.
What about kids’ calendars?
The most common pattern across the parents we’ve watched plan: one shared Apple Calendar called “Kids” or “Family,” populated with school events, sports practices, doctor appointments, and birthday parties. Both parents have edit access; both iPhones show every kid event automatically. Composed sits on top via Apple Calendar import (the bridge runs background sync every six hours), pulling in the family events and generating AI prep tasks for each one.
The bridge is one-way per composed-product-truth.md — Composed reads from Apple Calendar but doesn’t write back. That’s important to know: events you create inside Composed stay in Composed unless you re-create them in Apple Calendar, while events created in Apple Calendar (including shared family calendars) flow into Composed automatically. For most couples, the right pattern is to keep the shared family calendar in Apple Calendar where everyone already has access, and let Composed handle the prep + departure layer on top.
For one-off kid events that need an RSVP — a school conference one partner can attend, a birthday party with logistics, a parent-teacher pickup arrangement — Composed’s shared events work the same way as for partners: invite by text or email, the other partner RSVPs from the link, both see the prep checklist. The kids’ events that are recurring (every Tuesday soccer, every Thursday violin) belong on the Apple Calendar layer; the one-offs belong as Composed shared events.
If you’re the parent doing more of the household scheduling, the busy parents use case covers the broader patterns, and family scheduling goes into more depth on the calendar-plus-prep stack.
How does Composed compare to Cozi, TimeTree, and Maple for couples and families?
Cozi is the most-named family calendar app on the iPhone App Store. It does shared family calendars, shopping lists, and meal planning in one app. The shared calendar surface is functional, but it asks every family member to install Cozi and create an account — which is the friction point. Cozi has no AI prep tasks, no leave-by alerts, no screenshot-to-event flow, and no Apple Calendar bridge. It owns the data inside its own walls.
TimeTree is the visual-first alternative — a shared calendar with color-coded events, a chat layer inside each event, and a clean month view. It’s the most-downloaded couples calendar globally. TimeTree has no AI prep tasks, no departure intelligence, and limited Apple Calendar integration. The chat-inside-each-event is genuinely useful for coordination but turns each event into another small thread to manage. Compare with shared events without the group chat chaos.
Maple is a newer parent-coordinator app aimed at busy households. It does task assignment between parents, recurring chores, and a shared family calendar. Maple is closer to a household operating system than a planner; it doesn’t generate prep tasks for events and doesn’t compute departure time.
Apple Calendar with family sharing is the default fallback for iPhone couples and is genuinely enough for many households. Composed sits on top to add the preparation layer — prep checklists, departure alerts, three-layer reminders — without asking you to abandon Apple Calendar at all. The combination of Apple Calendar (for the recurring shared rhythm) plus Composed (for the per-event prep and departure) is the pattern that ends up working for most couples we’ve watched plan.
| App | Couples fit | What it adds | What it misses |
|---|---|---|---|
| Apple Calendar (family sharing) | Strong baseline | Free; already on every iPhone; iCloud sync | No prep tasks; basic time-to-leave; no RSVP |
| Google Calendar (shared) | Strong if cross-platform | Free; works on Android + iPhone; web access | No prep tasks; no leave-by; no native RSVP |
| Composed (shared events) | Strong layer | AI prep tasks; departure tracking; per-partner reminders; RSVP without app | Sharing is per-event, not per-calendar |
| Cozi | OK | Shopping + meal planning together | Asks everyone to install; no Apple Calendar bridge; no AI |
| TimeTree | OK | Visual; per-event chat; color coding | No prep; no departure; chat = more threads |
| Maple | OK for chore-heavy households | Task assignment between parents | Not a planner; no prep tasks; no departure |
If you want the deeper compare, Composed vs Google Calendar covers the layered-vs-replacement framing in detail.
When does sharing a single event beat sharing a whole calendar?
Share a whole calendar when both partners need ongoing passive visibility into the same set of recurring events — school pickups, family birthdays, work trips, recurring dinner reservations. The cost of sharing the whole calendar is low (you set it up once) and the value is the ambient awareness (“I know your work trip is next week without being told”).
Share a single event when the coordination is one-off and needs an explicit yes/no — a school conference, a friend’s birthday party, a doctor’s appointment one partner is driving the other to, a wedding RSVP that needs a clear “we’re both coming” or “I’m coming, she’s not.” The cost of sharing one event is one tap; the value is the explicit RSVP layer that calendar-sharing can’t provide.
The calendar invite is the minimum. What partners actually need is preparation and an explicit yes/no — and that looks different for every event.
The pattern most couples we’ve watched plan settle into: a shared Apple Calendar called “Family” for the recurring rhythm, Composed’s shared events for the one-off coordination, and the prep tasks layer running on both. Three things in their lanes, none of them trying to be everything. The household that runs this stack consistently is the household where one partner stops being the silent coordinator-in-chief.
Frequently asked questions
How do I share an Apple Calendar with my partner on iPhone?
On iPhone, open Calendar → Calendars → Add Calendar → Add Shared Calendar. Enter your partner's iCloud email address and set their permission level (View only or Edit). They'll receive an invitation in their Calendar app. Apple Calendar family sharing requires both partners to have Apple IDs and be signed into iCloud. Once accepted, every event added to that shared calendar appears automatically on both iPhones.
Can I share a Google Calendar event with someone who uses Apple Calendar?
Yes. Google Calendar invites send a standard iCalendar (.ics) attachment that Apple Calendar can read. Add your partner's email as a guest in Google Calendar, and they'll receive an invitation in Apple Calendar with Going/Maybe/No buttons. Composed's shared events work the same way — guests can download a .ics file from the RSVP page and add the event to Apple Calendar without installing Composed.
Does Composed generate prep tasks for events my partner created?
Yes. When your partner invites you to a Composed shared event and you accept, the event is added to your Composed library with the AI prep tasks already generated. If the event was created in your partner's Apple Calendar and synced to Composed via the calendar import bridge, Composed generates prep tasks against the imported event automatically — Composed's `generate-checklist` edge function runs against any event in your library, whether you created it or it arrived via sync or invitation.
Can my partner RSVP to a Composed event without installing the app?
Yes. Composed's shared events are designed so guests can respond without downloading the app. The organizer taps Share on an event, which generates a public RSVP link through the `share-event` edge function. The guest opens the link in any browser on iPhone, sees the event details, and chooses Going / Maybe / Not for me. The response writes back to the organizer's Composed instance immediately. The guest can also download a .ics file to add the event to Apple Calendar, or install Composed later if they want the prep tasks.
Why doesn't Composed write events back to Apple Calendar?
Composed's Apple Calendar bridge is one-way by design — Composed reads events from Apple Calendar through background sync every six hours, but it doesn't write back. The reasoning is in `composed-product-truth.md`: Composed is a preparation layer on top of your existing calendar, not a replacement for it. Events you create in Apple Calendar (including shared family calendars) flow into Composed automatically. Events you create directly in Composed live in Composed. That separation keeps the Apple Calendar surface clean for everyone in your family who's looking at it.
The household that ends up running calmly is rarely the household with the most-organized partner. It’s the household where the preparation is shared — where both partners know what’s coming, what to bring, and when to leave, without either of them having to be the one holding it all in their head. The right calendar setup is the one that distributes that work, not the one that just displays it. For the founder voice on how Jesse uses this in his own household, see Jesse’s about page.
