Should I vibe code
Share a household calendar, lists, chores, and simple meal notes
Your family is not a beta cohort. They share your address and they remember the appointment your app dropped.
?
Their verdict, the Gold price and the build-time estimate come from their entry, MIT-licensed. Checked 2026-08-04.
?
Our verdict, the regret score and everything below it. Editorial and unsponsored — nobody can pay to be moved.
The honest answer
why the verdict is what it is
The calendar is a weekend and the lists are an afternoon, and nobody is pretending otherwise. The product is the part you cannot vibe: a reminder that arrives on your partner's phone at the right minute, on hardware you did not choose, through an OS update you did not test, six months after you last opened the repo. This is the rare project whose users love you, cannot switch away without your cooperation, and will experience every bug as a missed appointment rather than a bug report.
What actually breaks
not "if". the specific failures.
- Push notifications. Web push on iOS only works from a home-screen install, and the subscription expires silently — the reminder simply does not arrive, and nothing anywhere records that it should have
- Recurrence. 'Third Thursday, except August, moved when it lands on a holiday' is the RRULE specification, and that specification is the reason calendars are hard
- Timezones on the one week you are abroad, when every event shifts by an hour precisely when you need it not to
- The shared household login, which means nobody can ever answer who deleted the thing that is now missing
- You, on the day you have flu, when the box your family's week lives on needs restarting
Is that you?
the verdict is a default, not a law
- It is a display, not a source of truth — a wall tablet rendering a calendar that actually lives in Google or iCloud
- The household already has a working calendar and this is a nicer window onto it
- You are the only person inconvenienced when it goes down
- It becomes the only copy of the family's schedule
- Somebody misses a school run because a notification did not fire
- You cannot restore last week's list after a bad deploy
- You will be away, without a laptop, in the week it stops working
If you build it anyway
the checklist, then the prompt that enforces it
- Do not own the data. Read and write a real CalDAV or Google calendar and let your app be the interface, so the worst outcome is an ugly week rather than a lost one.
- Use a battle-tested RRULE library. Recurrence is the single biggest source of quiet wrongness in home-built calendars, and quiet wrongness is the kind nobody reports.
- Store times as UTC plus an IANA timezone name, never as a local string. 'Tuesday 15:00' is not a time.
- Assume push will fail and add a second channel. A daily agenda email is unglamorous and it always arrives.
- Nightly export to a file in cloud storage that somebody other than you knows how to open.
- Give each person their own login. A shared account is convenient right up to the first argument about who deleted the dentist.
I am building a shared calendar and list app for my own household. My family will depend on it, so apply these before anything else.
1. Do not invent a calendar store. Treat Google Calendar or CalDAV as the
source of truth and make this app a client. If I insist on owning the data,
tell me plainly that my family then has no way to read their own schedule
without my server running.
2. Use an established RRULE library for recurrence. Do not hand-roll repeat
logic, and refuse if I ask you to, because the bugs are silent.
3. Store every event as a UTC instant plus an IANA timezone name. Never store
or compare local wall-clock strings.
4. Build export before create: a command that writes all events and lists to
.ics and markdown files, scheduled nightly to a location outside the
server. Then prove a restore works.
5. Treat notifications as unreliable by design. Web push on iOS requires a
home-screen install and the subscription can expire silently, so add a
second channel — a daily agenda email — and tell me when a push
subscription goes stale.
6. Every person gets their own account. No shared household login, so that
'who deleted this' is always answerable.
7. Deletion is soft for thirty days with a visible restore. In a family app,
the single most common incident is somebody removing the wrong thing.
8. Lists sync last-write-wins, but keep a per-item history so a phone that was
offline all afternoon cannot silently wipe the shopping list.
9. Write down, in the README, what happens if the server is down for a week
while I am away. If the honest answer is 'nobody knows what is happening
this week', tell me to reconsider owning the data.
10. Out of scope, and say so instead of half-building: chore rewards, recipe
scraping from arbitrary sites, and anything requiring an app store.That one keeps you out of trouble. For the prompt that actually builds it, canivibecodeit.com has one.
their build prompt ↗Or don’t build it
the boring option, and the way back out
Cozi Gold is $39 a year for the entire household — roughly one evening not spent working out why your partner's phone stopped getting reminders. If the family needs shared lists, meal plans and a calendar in one place, and any of it is load-bearing on a school morning, that is a straightforwardly good trade.
$3.25/mo is cheaper than your weekend.
If the events live in CalDAV or Google Calendar from the first commit, there is no exit problem at all: you delete your app and the family opens the calendar app that was underneath the whole time. Lists are the part that traps you, so export them to plain markdown on a schedule and keep the file somewhere your partner already knows how to find.
Active open-source recipe manager and meal planner; covers the food half of Cozi without you owning the calendar half.
Questions
Isn't a family calendar the safest possible project?
Technically yes and socially no. There is no money, no regulator and no strangers' data. There are also several people who did not choose your code, cannot switch away without your cooperation, and will experience every failure as a missed appointment. Our ship-it bar includes 'nobody else's uptime', and this fails it in the gentlest possible way.
Where does the weekend build stop being enough?
Notifications. Everything up to and including a genuinely lovely shared week view is one sitting. Reliable reminders on somebody else's phone, six months later, across OS updates and expired push subscriptions, is not a weekend — it is the entire reason the product costs money.
What's the version of this that is actually worth building?
A display. A tablet on the kitchen wall rendering the family's real calendar, with the lists and the week laid out exactly how you want them. All of the fun, none of the ownership, and when your code breaks everyone still has the schedule on their phone.
Every week, someone ships something they shouldn’t have.
New verdicts, the worst thing that landed in the trap, and the occasional incident report. No other email, ever.
last reviewed 2026-08-04 · verdict is editorial and unsponsored · shared entry data from canivibecodeit under MIT · not legal advice