Someday is a free-to-host, open-source calendar availability picker built on Google Apps Script for Gmail users, and it is aimed at individuals, small teams, and developers who want a Calendly-style booking page without paying for or operating a separate scheduling service.

What it is

Someday is an open-source scheduling tool designed specifically for Gmail users. It is hosted on Google Apps Script as a web app and managed with clasp, the Apps Script command-line tool. The frontend is written in TypeScript and built with React, Shadcn/UI, and Vite, and the project is distributed under the MIT licence in the Business Software / Scheduling & Event Management category. The topics attached to the repository are google-apps-script, react, scheduling, shadcn-ui, typescript, and vite, which matches the stack described in the README.

The concrete problem it solves is the cost and the data path of a hosted booking service. The README describes Someday as a simple alternative to traditional scheduling apps such as Calendly, and its pitch is that hosting is free through a Google account rather than through a paid scheduling vendor. Availability is read from Google Calendar by a Apps Script web app pointed at the primary calendar by default, and a visitor picks a date and time slot and submits a short form containing a name, email, phone number, and an optional note. Because the whole loop runs inside Google Apps Script and Google Calendar, the project states that no data is shared with third-party apps beyond Google itself.

Key capabilities

• Free hosting: the app runs as a Google Apps Script web app, so hosting costs nothing beyond the Google account that owns it.
• Availability configuration in backend/src/app.ts through four variables: CALENDAR, TIME_ZONE, WORKDAYS, WORKHOURS, plus TIMESLOT_DURATION.
• Booking flow where a visitor selects a date and time slot and submits a form with name, email, phone, and an optional note.
• Apps Script backend function fetchAvailability in dist/app.gs, which must be run once to complete the OAuth authorization and calendar access consent.
• Self-hosted iframe option: hosted-iframe-example.html embeds the script in your own page, with GitHub Pages suggested as a host, to remove the "This application was created by a Google Apps Script user" banner.
• clasp-based deployment: clasp create --type webapp followed by npm run deploy publishes the web app.
• Development mode with generated dummy data via generateDummyData in frontend/hooks/useGoogleTimeSlots.ts, so the UI can run without live calendar access.

Who uses it and how

• Gmail and Google Calendar users who want a booking link but do not want to pay for a scheduling subscription, and who are content to have availability read from their own calendar.
• Developers extending the project, who change the workday, work hour, and timeslot settings in backend/src/app.ts and redeploy with npm run deploy.
• Teams that want the interface embedded in an existing site, using the iframe example and hosting the HTML themselves.
• Privacy-conscious users, since the README states data is not shared with third-party apps beyond Google.
• Contributors working on the React and TypeScript frontend, who run cd ./frontend, npm install, and npm run dev against mock data.

Getting started

Install clasp globally with npm install -g @google/clasp@^2.5.0, log in with clasp login, enable the Apps Script API, then create a web app project with clasp create --type webapp and publish it with npm run deploy. A browser demo with mocked endpoints is available at https://someday-demo.vercel.app.

How it compares

The README positions Someday against Calendly and against cal.com, presenting it as a simpler alternative for Gmail users rather than a full scheduling platform. On the axes the facts support, the difference is hosting and cost model: Someday is MIT licensed and hosted on a Google Apps Script account at no charge, whereas the named alternatives are conventional hosted scheduling products. Ownership follows from that choice, because availability lives in Google Calendar and the app runs under the user's own Google account.

When to use it — and when not to

Choose Someday if your calendar already lives in Google and you want a booking page you can deploy and host for free, accepting that setup means enabling the Apps Script API, running fetchAvailability once to grant calendar authorization, and dealing with the Google consent screens. Skip it if you are not a Gmail or Google Calendar user, if you need a richer booking product, or if you do not want to operate an Apps Script project at all — the install flow is manual, and the README excerpt ends mid-sentence when describing how to add calendars other than the primary one.

// backend/src/app.ts
const CALENDAR = "primary";
const TIME_ZONE = "America/New_York";
const WORKDAYS = [1, 2, 3, 4, 5];
const WORKHOURS = {
  start: 9,
  end: 13,
};
const TIMESLOT_DURATION = 30;