No. You can sign up with just an email and password — or with Google if you prefer. Connecting a Google calendar is completely optional: it's one of several source types, alongside iCal/ICS feeds (school, sports, work) and events you add yourself. Plenty of people use Tapestry without ever connecting Google.

A native iOS app is in progress. In the meantime, Tapestry works great in your phone's browser — open app.tapestrycal.com and use "Add to Home Screen" for an app-like experience.

Free during early access. If that ever changes, existing users will be notified and grandfathered into something fair.

Most team and league apps publish each team's schedule as an iCal/ICS feed — in TeamSnap it's under Account → Settings → Calendar Sync; LeagueApps, PlayMetrics, SportsEngine, and others have a similar "subscribe" or "calendar feed" link. Copy that URL, paste it into Tapestry's Sources page, and include it in your views. The step-by-step walkthrough uses TeamSnap but works the same for any of them.

Use smart import. Paste anything with dates — an email, a flyer, a web page — or upload a file, and Tapestry reads the schedule and extracts the events for you. You review exactly what was found before anything is added, and when a new version of the schedule comes out, re-upload it to update the source in place.

No. Every source — Google, iCal/ICS feeds, all of it — is read-only. We pull events in; we never write back. Edits you make in Tapestry live in our database as per-event overrides and survive future syncs from the source.

The credential is revoked and removed. Any source feeds that were using it stop syncing but stay in your workspace, so you can reconnect later without rebuilding everything.

A view is a composed calendar: pick which sources it includes — or pull in events by category, person, or tag — then add rules that rename, recolor, exclude, tag, or classify matching events. Rules are transparent, and they never touch the original calendars. Start with building rules that don't break, or see a full worked example in the Kids' Activities walkthrough.

Yes. Every workspace member can add their own sources — a Google account, ICS feeds, whatever they like. Connected sources are visible to the workspace, so anyone can build a view that includes the family's calendars, but only the person who added a connection can remove it.

Yes. Every view exports a private ICS subscription URL that any standards-compliant calendar app can consume — Apple Calendar, Outlook, or Google Calendar. Each event's title (including emoji), date and time, location, and notes travel with it, along with any rule-driven text changes like renames or name prefixes.

Most of it does. Titles (with emoji and any rule-based renames), dates, times, locations, and notes always carry — and we fold the birthday age into the title and list the assigned people in the event's notes, so those come through too. We also send a per-event color, which apps that support per-event colors (Apple Calendar and friends) will honor. The exception is Google: it paints a subscribed feed in one color you choose and ignores per-event colors — so for a Google-bound feed, lean on names-in-titles for differentiation. Categories ride along as a standard tag too (Apple shows them; Google doesn't). More in optimizing a view for Google Calendar.

Yes. Open any event and choose "Remind me" — 15 minutes, 1 hour, 24 hours, or 1 week before, or a custom lead time — and Tapestry emails you before it starts. You can also set default reminders for every event from a source (never miss a practice), or account-wide defaults in Account Settings. Reminders are personal: your choices never ping the rest of your workspace. Push notifications arrive with the iOS app.

Yes. Mark any event as a task — "add salt to the water softener", "rotate the tires" — and every occurrence gets its own checkbox. Check occurrences off as you complete them, and filter or hide completed items when you want a clean view.

Passwords are hashed — never stored in plain text — and sessions are HMAC-signed, HttpOnly, Secure cookies. If you connect a Google calendar, that token is encrypted at rest with a per-deployment key. All workspace access is gated by membership — co-members see what's in the shared workspace and nothing else. You can delete your account, or any workspace you own, at any time.