Whether you are writing yet another one task tracker or calendar app, or simply want to offer the users to skip the joy of using UIDatePicker and let them quickly and efficiently select dates — CrispyCalendar is the calendar UI framework you need.
CrispyCalendar alternatives and similar libraries
Based on the "Calendar" category.
Alternatively, view CrispyCalendar alternatives based on common mentions on social networks and blogs.
CalendarKit8.7 4.4 L5 CrispyCalendar VS CalendarKit📅 Calendar for Apple platforms in Swift
HorizonCalendarA declarative, performant, iOS calendar UI component that supports use cases ranging from simple date pickers all the way up to fully-featured calendar apps.
DateTimePicker8.3 0.0 L2 CrispyCalendar VS DateTimePickerA nicer iOS UI component for picking date and time
Koyomi6.6 0.0 L3 CrispyCalendar VS KoyomiSimple customizable calendar component in Swift
ElegantCalendarThe elegant full screen calendar missed in SwiftUI.
KVKCalendar5.4 8.3 CrispyCalendar VS KVKCalendarA most fully customization calendar for Apple platforms 📅
Workaholic2.9 0.0 CrispyCalendar VS WorkaholicA Github's like work contribution timeline. 🤸🏻
PTEventView1.0 0.0 CrispyCalendar VS PTEventViewAn Event View based on Apple's Event Detail View. Written in Swift 3. Supports ARC, Autolayout and editing via StoryBoard.
Appwrite - The Open Source Firebase alternative introduces iOS support
* Code Quality Rankings and insights are calculated and provided by Lumnify.
They vary from L1 to L5 with "L5" being the highest.
Do you think we are missing an alternative of CrispyCalendar or a related project?
Whether you are writing yet another one task tracker or calendar app, or simply want to offer the users to skip the joy of using
UIDatePicker and let them quickly and efficiently select dates — CrispyCalendar is the calendar UI framework you need.
- Written with localization in mind. Specifically, many various (and even nonsensical) combinations of calendar types, locale identifiers and writing directions were tested. Also, this framework does not contain a single translation error simply because only standard Apple frameworks (hence, their translations) are being used and none of third-party code.
- Ease of integration, customization options and extensibility — you are free to choose any and all of those. The framework contains out-of-the-box components for the most common tasks; in many cases a single line of code allows you to employ rich user interfaces, allowing you to concentrate on business logic implementation. But at the same time, every such solution is thoroughly equipped with tuning possibilities and is designed modularly, allowing you to freely reuse and combine basic blocks to suite your specific requests.
- Optimized for performance. Even seasoned devices like iPhone 5 are rendering the calendar at the acceptable frame rate to say the least. Minor sacrifices had to be made to achieve that, but the overall result is shining nonetheless.
- Objective C support. Whether you are constrained by legacy code or just not ready for Swift in production-grade code yet, using CrispyCalendar from Objective C is possible. Mostly, Swift-specific features only are missing, but blind spots here and there are possible.
- Common usage patterns and various examples of code can be found in [Demo project](CrispyCalendar.xcodeproj).
- API Reference contains detailed
descriptions of the vast majority of
opentypes and identifiers.
CocoaPods is a dependency manager for Swift and Objective-C Cocoa projects. It has over 53 thousand libraries and is used in over 3 million apps. More details and installation instructions may be found here: Using Cocoapods.
To integrate CrispyCalendar into your Xcode project using CocoaPods, specify it in your Podfile:
source 'https://github.com/CocoaPods/Specs.git' platform :ios, '10.3' target 'TargetName' do pod 'CrispyCalendar', '~> 1.0.2' end
Then, run the following command:
$ pod install
Open [Demo project](CrispyCalendar.xcodeproj) in Xcode and build
CrispyCalendar framework target.
Then, embed it into your project and add it to
Linked Frameworks and Libraries section of app target.
All the fonts, colors and other appearance details are customizable via corresponding properties. CPCCalendarView does also support customization via UIAppearance for properties representable in Objective C.
DefaultBasic from Debt ControlInput view from Debt Control
Prebuilt UI commonly uses CPCMonthView capable of displaying single month. CPCMultiMonthsView may be used as container for month views allowing shared selection handling and other functionality.
Single day selectionDays range selection
Ordered & unordered selection
Selection process is fully controlled externally by corresponding view's delegate. Note that delegates for views inside containers are not supported.
Unordered selectionOrdered selection
Custom draw handlers
CPCMonthView does not comprise any real child views but is logically drawn from title "label" and "grid", consisting of "day cells". Custom day rendering is supported via custom CPCDayCellRenderers.
Custom cell renderer example
Locale used by any component cannot be set explicitly, but Calendar's locale is honored. The framework uses
[[[NSBundle mainBundle] preferredLocalizations] firstObject] as default locale, including setting it for calendars without explicitly set locale.
Non-gregorian calendar rendering
Available dates limiting, RTL and landscape orientation are fully supported.
Dates limitingColumned mode
CrispyCalendar is owned and maintained by the Cleverpumpkin, Ltd.
CrispyCalendar was originally created by Kirill Bystrov as a response to lack of quality calendar-rendering libraries. Android couterpart does exist (but neither API nor UX is similar), check it out here: CrunchyCalendar.
CrispyCalendar is released under the MIT license. See [LICENSE](./LICENSE) for details.
*Note that all licence references and agreements mentioned in the CrispyCalendar README section above are relevant to that project's source code only.