A calendar screen looks like a grid with coloured boxes, and most of the work is in the cases the grid does not show. Three meetings overlap at 10:00 and each needs its own column. An event lasts three days and has to span cells. The user long-presses a box and drags it to another day. "Every weekday at 08:30, except the 25th" has to become real occurrences. In Arabic, the days run right to left and the time labels move to the other side. And a screen-reader user needs to hear each event and be able to move it without dragging.

time_grid_calendar is a Flutter package with day, 3-day, week and month views, similar to Google Calendar. Events can overlap, be dragged and resized, and repeat with RRULE rules. The views work right-to-left and with screen readers, and the package has no commercial dependencies.

What it does

Generic events. CalendarEvent<T> has an id, start, end, all-day flag, title, colour and a typed payload, so you can attach your own model to each event. Events come from an EventController, or from a synchronous or asynchronous range loader, loadEvents(DateTimeRange).

TimeGridView, for 1 to 7 days. One widget covers the day, 3-day and week views:

  • Hour height, start and end hour, and time labels (12-hour or 24-hour, locale-aware through intl) are configurable.
  • Overlapping events sit side by side. The view uses the standard layout: clusters, greedy column assignment, then expansion into free columns.
  • A pinned all-day row grows to fit, and multi-day bars span their days.
  • There is a now line, and the grid scrolls to the current time when it opens.
  • You swipe between date ranges with a PageView, and the vertical scroll position is kept.
  • Tapping an empty slot creates an event, snapped to 15 or 30 minutes, or any divisor of 60.
  • Long-press and drag moves an event, and dragging its bottom edge resizes it. Both snap, and your callback can veto the change.
  • eventBuilder replaces the tile content.

MonthView. A 6×7 grid. The first day of the week follows the locale. Multi-day events are bars spanning cells, extra events collapse into "+N more", and days, events and "+N more" can all be tapped.

Navigation pieces. WeekdayHeader, CalendarViewController (next, previous, jump to a date, and the visible range), and CalendarNavigation (visible days, and range titles such as "Sep – Oct 2026").

Recurrence. RRULE expansion happens in wall-clock time, so "every day at 09:00" stays at 09:00 across DST changes. It is built on the maintained rrule package and adds WKST other than Monday, date-only UNTIL and EXDATE. RecurringEventSeries expands a master event, and you can override single occurrences through the controller.

Localisation. RTL layouts mirror: time labels move to the right and days run right to left. Day names, month names and times come from intl, for example in French and Arabic. Screen-reader labels are bundled in English, French and Arabic.

Accessibility. Every event has a semantics label with its title and time range. Tab moves focus between events, arrow keys move them, Shift plus the up or down arrow resizes them, and Enter or Space opens them. Screen readers get custom actions: move earlier, move later, move to the previous day, move to the next day, shorten and extend.

Performance. Only the visible page is built, and a day's layout is cached by day and by a hash of its events.

How to use it

Add it from GitHub:

dependencies: time_grid_calendar: git: https://github.com/AbdeldjalilChougui/time_grid_calendar 

For French, Arabic and other locales, add flutter_localizations to your app as usual.

A week view with one event, one recurring series and the editing callbacks:

import 'package:flutter/material.dart'; import 'package:time_grid_calendar/time_grid_calendar.dart'; class _WeekPageState extends State<WeekPage> { final events = EventController<String>(events: [ CalendarEvent( id: '1', start: DateTime(2026, 9, 24, 9), end: DateTime(2026, 9, 24, 10, 30), title: 'Design review', color: Colors.teal, payload: 'room 4', ), ]); final view = CalendarViewController(); @override void initState() { super.initState(); events.addSeries(RecurringEventSeries( master: CalendarEvent( id: 'standup', start: DateTime(2026, 9, 1, 8, 30), end: DateTime(2026, 9, 1, 8, 45), title: 'Standup', ), rrule: 'FREQ=WEEKLY;BYDAY=MO,TU,WE,TH,FR', exdates: [DateTime(2026, 9, 25, 8, 30)], )); } @override Widget build(BuildContext context) { return Scaffold( body: TimeGridView<String>( controller: events, numberOfDays: 7, // 1 = day, 3 = 3-day, 7 = week snapMinutes: 15, viewController: view, onSlotTap: (start) => events.add(CalendarEvent( id: '${start.millisecondsSinceEpoch}', start: start, end: start.add(const Duration(hours: 1)), title: 'New event', )), onEventTap: (e) => debugPrint('${e.title} ${e.payload}'), // Return false, or a Future of false, to veto the change. onEventMove: (event, newStart, newEnd) => true, onEventResize: (event, newStart, newEnd) async => true, ), ); } } 

This is the README's example without the app bar and the dispose method. In your own code, dispose both controllers, and call view.previous and view.next from your buttons.

A month view with an asynchronous loader:

Widget month(Future<List<CalendarEvent<String>>> Function(DateTimeRange) fetch) => MonthView<String>( loadEvents: fetch, // called once per visible 6-week range onDayTap: (day) => debugPrint('day $day'), onEventTap: (event) => debugPrint(event.title), onMoreTap: (day, events) => debugPrint('${events.length} on $day'), ); 

To reload loader data, build an EventController<T>.withLoader(...) yourself and call reload().

The recurrence engine also works without the widgets:

final starts = expandRecurrence( rrule: 'RRULE:FREQ=MONTHLY;BYDAY=-2MO;COUNT=6', start: DateTime(1997, 9, 22, 9), rangeStart: DateTime(1997, 1, 1), rangeEnd: DateTime(1999, 1, 1), ); 

How times are interpreted

This is the design decision to understand before you use the package: it does not use time zones. It reads a DateTime only through its fields (year, month, day, hour, minute), never as an instant, and does day and minute arithmetic on those fields. Two consequences follow:

  • An event at 09:00 is drawn at 09:00. A recurring 09:00 event stays at 09:00 across daylight-saving changes.
  • Keep every value in one calendar either local or UTC. UTC-flagged values used as floating wall-clock times are the most robust choice: local DateTimes cannot represent a time that falls in a spring-forward gap (Dart turns 02:30 into 03:30), and UTC values can.

UNTIL values in rules are read as wall-clock times too, with or without a trailing Z.

Things to know

  • There is no time-zone conversion. Convert to wall-clock values before you hand events to the views.
  • WKST support is partial. A WKST other than MO is supported for WEEKLY rules with BYDAY, because that is where RFC 5545 says it matters. It is not supported together with BYWEEKNO, BYSETPOS or the other BY* parts on those rules, and those combinations throw a FormatException.
  • Not included: RDATE, EXRULE and full iCalendar parsing.
  • Hijri calendar display is not included.
  • Dragging stays on the visible page. To move an event further, use the keyboard or semantics actions, or page first and then drag.
  • Events that cross midnight are drawn in each day's column in the time grid. They do not appear in the all-day row.
  • What the tests check. The recurrence tests check the worked examples in RFC 5545, section 3.8.5.3. No data sets are bundled: first days of the week and date formats come from the CLDR data that ships with the intl package.

Why I built it

The README's first paragraph ends with "No commercial dependencies", and that is the problem in short: a calendar with a time grid, overlapping events, drag and resize, and recurrence, under an MIT license, with nothing to buy.

The other part is what often gets left for later. RTL is not a flag added at the end here: the grid mirrors, and the labels come from intl. Accessibility is not only labels: every drag action has a keyboard shortcut and a screen-reader action, so moving an event does not require a finger on the screen. And recurrence is treated as wall-clock time on purpose, because a 09:00 standup that shifts by an hour twice a year is the kind of bug users notice.

Get the code

The source, the example and the tests are on GitHub: https://github.com/AbdeldjalilChougui/time_grid_calendar. It is MIT licensed. Issues and pull requests are welcome.

Originally published at abdeldjalilchougui.biz.