Open-source project
airbnb/HorizonCalendar avatar
airbnb/HorizonCalendar

HorizonCalendar: Airbnb's iOS Calendar Component Reviewed

A declarative, performant, iOS calendar UI component that supports use cases ranging from simple date pickers all the way up to fully-featured calendar apps.

3,168 stars263 forksSwiftApache-2.0

At a glance

What is it?
HorizonCalendar is an Apache-2.0 Swift calendar UI component from Airbnb, distributed via Swift Package Manager, CocoaPods and Carthage. It is a strong fit when the calendar is the product; it is heavier than a simple date picker needs.
Who is it for?
Adopt HorizonCalendar if the calendar is a first-class surface in your iOS app and you need custom day cells, range highlighting, overlays or horizontal paging. Do not adopt it for a one-off date picker, or if you cannot support iOS 11 or later and Swift 5 or later.
Can I use it commercially?
Yes. Apache-2.0 is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
Is it still maintained?
Yes. The repository last received commits 27 days ago.
What is it written in?
Mainly Swift, according to GitHub's language statistics.

Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.

From daily snapshots

Star history

  • airbnb/HorizonCalendar3,168 ★ · +10
Star history
Repository2026-09-252026-11-15
airbnb/HorizonCalendar3.2k3.2k

10 Stars in the last 51 days, measured from the daily GitHub snapshot. Compare with other projects

Editorial analysis

What HorizonCalendar Is For

HorizonCalendar is a calendar UI component for iOS, written in Swift and published under Apache-2.0. The README states it is used to implement every calendar and date picker in the Airbnb iOS app, which is a useful signal about the range it is expected to cover: a stay search view, an availability calendar, a wish list, an experience reservation flow and a host calendar management screen all appear in the README's screenshots.

The intended audience is iOS engineers building a calendar into an app rather than consuming one off the shelf. The component is declarative, and the README describes the API as encouraging unidirectional data flow for updating calendar content. That framing matters: you describe what the calendar should contain, and the component reconciles the display, including animated content updates.

It is not a scheduling service, not a backend, and not a cross-platform view. There is no Android or web target in the repository layout. If you need a calendar that works outside an iOS app, this is the wrong tool, and the README makes no claim otherwise.

How the Declarative Model and Layout Work

The component separates layout from content. Layout is controlled through customizable layout metrics, and the README lists vertical month layouts, horizontal month layouts, and paging for the horizontal layout. A days-of-the-week row can be pinned to the top, and a separator can be placed below it.

Content is supplied through customization points. The README lists customizable default views for days, month headers, days of the week and a month grid background, plus the ability to specify custom views for individual days, month headers, days of the week, range highlights, overlays and month or day background decorations. That is a wide surface, and it is the main reason the component exists: a stock calendar control rarely matches a designed product surface.

Selection is handled through callbacks. The README describes a day selection handler for taps and a multi-day selection handler for drag gestures. Scrolling is also exposed: the component can scroll to arbitrary dates and months, with or without animation. Date ranges are not bounded in practice, since the README states it supports large, virtually-infinite date ranges, and it can show partial boundary months, giving the example of exactly 2020-03-14 to 2020-04-20.

Calendar systems come from Foundation.Calendar. The README states all calendars from Foundation.Calendar are supported, naming Gregorian, Japanese and Hebrew. Right-to-left layout is supported, and the README lists accessibility support as a feature, with a dedicated accessibility testing section in the table of contents.

Installing HorizonCalendar and Rendering a First Calendar

Requirements come first. The README lists a deployment target of iOS 11.0 or later, Swift 5 or later, and Xcode 10.2 or later. All three installation routes are documented, and the choice is mostly about what your project already uses.

With Swift Package Manager, the README gives this line to add to your Package.swift:

swift
.package(name: "HorizonCalendar", url: "https://github.com/airbnb/HorizonCalendar.git", from: "1.0.0"),

With CocoaPods, add the pod to your Podfile:

ruby
pod 'HorizonCalendar'

With Carthage, add the repository to your Cartfile:

code
github "airbnb/HorizonCalendar"

After the dependency is integrated, the README's basic setup has three steps: import the module, instantiate the view, and add it to your view hierarchy. The README shows these as separate subsections rather than a single snippet, so the exact initializer and configuration calls are in the integration tutorial rather than reproduced here.

For a first real look at behaviour, the README points to the example app at ./Example/HorizonCalendarExample.xcworkspace. It explicitly warns to open the .xcworkspace file and not the .xcodeproj file, because the project file does not have access to HorizonCalendar.framework. The example app contains demo view controllers for single day selection, day range selection, a selected day tooltip, and scrolling to a day with animation, each in vertical and horizontal variants.

Where HorizonCalendar Gets Awkward

The cost of the customization surface is that you build the calendar's appearance yourself. Default views exist, but the README's feature list is dominated by things you specify: custom day views, month headers, weekday views, range indicators, overlays, month background decorations and day background decorations. A team expecting a finished calendar look will spend time on view code.

The declarative model has a second cost. Animated content updates and unidirectional data flow mean the calendar's state lives in your model, and you re-render by describing new content. If your app mutates calendar state from several places without a single source of truth, you will fight the component rather than benefit from it.

Platform constraints are real. iOS 11.0 or later, Swift 5 or later and Xcode 10.2 or later are the documented floor. There is no mention of macOS, tvOS or watchOS support in the README's requirements, and the repository layout shows no such targets.

Finally, there is a documentation gap around change management. The repository contains a CHANGELOG.md at the top level, and the repository has no published releases, so anyone planning an upgrade should read that file rather than assume a published release history. The README does not document rollback or migration steps between versions.

HorizonCalendar Compared with FSCalendar and UICalendarView

The most common alternative in iOS work is FSCalendar, which appears in the related searches for this project. The difference is in the model. FSCalendar presents a calendar control with a delegate and data source style API and a set of built-in appearance properties. HorizonCalendar asks you to supply views and describes content declaratively, which is more work up front and more control afterwards. If your design is close to a standard calendar, FSCalendar will get you there with less view code. If your design is not standard, HorizonCalendar's customization points are the reason to pick it.

UICalendarView is Apple's own calendar view, and it is the natural comparison for apps that only target recent iOS versions. Its advantage is that it ships with the platform and needs no dependency. Its constraint is the same: you get Apple's view, with the customization Apple exposes. HorizonCalendar exists precisely in the space where that is not enough, and it supports iOS versions older than UICalendarView's availability.

JTAppleCalendar, CalendarKit and ElegantCalendar also appear in the related searches, but this article does not describe their internals, so no comparison beyond naming is honest. What can be said is that HorizonCalendar's distinguishing claim is the combination of a declarative API, virtually-infinite date ranges, and overlay and decoration customization points in one component.

Licence, Maintenance and Upgrade Cost

HorizonCalendar is licensed under Apache-2.0. That is a permissive licence, and it is the same licence family used across many Airbnb open source projects. It permits commercial use, and it includes a patent grant, which matters for some legal teams. This is not legal advice; check the LICENSE file in the repository with your own counsel if the patent terms affect you.

The repository is not archived, and the last push was on 2026-09-03. That is recent enough that the project is not dormant, but the listing retrieved no releases, so there is no published version history to plan upgrades against. The practical upgrade cost therefore sits in CHANGELOG.md, which is present at the top level of the repository, and in the version constraint you choose at install time. The README's Swift Package Manager example pins from "1.0.0", which is a floor rather than a ceiling; if you want to control when the component changes, pin a narrower range in your own manifest.

Because the component is view-layer only, an upgrade does not touch networking, persistence or business logic. The risk surface is rendering and layout, which is why the example app is the fastest way to check a new version against the demos before you ship it.

Editorial conclusion

Adopt HorizonCalendar if the calendar is a first-class surface in your iOS app and you need custom day cells, range highlighting, overlays or horizontal paging. Do not adopt it for a one-off date picker, or if you cannot support iOS 11 or later and Swift 5 or later. Before committing, open Example/HorizonCalendarExample.xcworkspace and confirm the demo view controllers match your design, and read CHANGELOG.md because the repository has no published releases.

Frequently asked questions

How do I install HorizonCalendar in an iOS project?

The README documents three routes: Swift Package Manager, CocoaPods and Carthage. For Swift Package Manager you add a package dependency pointing at the GitHub repository, for CocoaPods you add pod 'HorizonCalendar' to your Podfile, and for Carthage you add github "airbnb/HorizonCalendar" to your Cartfile.

What iOS and Swift versions does HorizonCalendar require?

The README lists a deployment target of iOS 11.0 or later, Swift 5 or later, and Xcode 10.2 or later. There is no mention of macOS, tvOS or watchOS support.

Does HorizonCalendar support both SwiftUI and UIKit?

Yes. The README lists SwiftUI and UIKit support as a feature, and the integration tutorial's basic setup covers importing the module, instantiating the view and adding it to your view hierarchy.

Official sources

  1. airbnb/HorizonCalendar on GitHub
  2. Issues
  3. License: Apache-2.0
  4. README
Add this badge to your README

If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.

Add this badge to your README

markdown
[![Hysen Labs](https://hysenlabs.com/badge/airbnb-horizoncalendar.svg)](https://hysenlabs.com/projects/airbnb-horizoncalendar)

Star history chart for your README

markdown
[![Star history](https://hysenlabs.com/chart/airbnb-horizoncalendar.svg)](https://hysenlabs.com/projects/airbnb-horizoncalendar)

Was this useful?