Skip to main content

Migrating from FullCalendar to Mobiscroll

Overview​

This article provides a comprehensive guide for migrating your scheduling solution from FullCalendar to Mobiscroll. It highlights the key differences between the two libraries and outlines step-by-step instructions, covering installation, configuration, resources, events, and features, ensuring a smooth and informed transition.

Installation​

Migrating from FullCalendar to Mobiscroll starts with a different approach to installation, especially regarding package access and tooling.

Mobiscroll installation steps:​

Install the Mobiscroll CLI (only needed once):

npm install -g @mobiscroll/cli

Configure Mobiscroll in your project (navigate to your project root folder and run):

mobiscroll config javascript

Alternatively, Mobiscroll also supports manual installation if you’re not using NPM. However, using NPM is generally the recommended approach for simplicity and maintainability.

Initialization​

FullCalendar:​

const calendar = new Calendar(container, {
  // ...
});

Mobiscroll:​

mobiscroll.eventcalendar('#container', {
    // ...
});

View configuration​

Key Differences:

  • With Mobiscroll, you get precise control over time ranges on Scheduler and Timeline views, plus feature-rich Event Calendar and Agenda views for seamless scheduling.
  • FullCalendar uses plugins and view-specific options. Standard calendar layouts such as month, week, day, and list are available through separate packages, while timeline and resource-based scheduling require Premium plugins.

FullCalendar Timeline view:​

In FullCalendar, the Timeline view is configured through the initialView, slotMinTime, and slotMaxTime options. Resource-based timeline scheduling also requires the resourceTimelinePlugin and a resources array.

const calendar = new Calendar(container, {
  plugins: [ resourceTimelinePlugin ],
  initialView: 'resourceTimelineDay',
  slotMinTime: '06:00:00',
  slotMaxTime: '20:00:00',
  initialDate: '2017-01-01'
});

Mobiscroll Timeline view:​

In the Mobiscroll Timeline view, the timeline object within the view option allows you to customize the visible days and the timeline’s scale. You can specify which days to display (e.g., weekdays), set the time scale (e.g., 30-minute intervals), and define the frequency of the labels shown (e.g., every 15 minutes).

mobiscroll.eventcalendar('#container', {
    view: {
        timeline: {
            type: 'day',
            size: 1,
            startTime: '06:00',
            endTime: '20:00'
        }
    },
    defaultSelectedDate: '2017-01-01' // if you want to set the initial view to a specific date
});

Check out how you can configure the Timeline view in this live example.

FullCalendar TimeGrid view:​

For a scheduler-style week layout in FullCalendar, the most common setup is timeGridWeek and this need to be specified with the initialView. You choose the initial date with initialDate.

const calendar = new Calendar(container, {
  plugins: [timeGridPlugin],
  initialView: 'timeGridWeek',
  initialDate: '2020-09-12'
});

Mobiscroll Scheduler:​

You can customize the visible days and hours, as well as the time grid scale, using the schedule object under the view option. This allows you to define which days are shown (e.g., weekdays), set the visible time range (e.g., 8 AM to 6 PM), adjust the time scale (e.g., 30-minute intervals), and control the frequency of the labels (e.g., every 15 minutes).

mobiscroll.eventcalendar('#container', {
    view: {
        schedule: {
            type: 'week'
        }
    },
    defaultSelectedDate: '2020-09-12' // if you want to set the initial view to a specific date
});

Check out how you can configure the Scheduler view in this live example.

Overall Mobiscroll has more built-in breakpoint-specific configuration.

Resource configuration​

Migrating resource data from FullCalendar to Mobiscroll should be relatively straightforward.

FullCalendar – resource definition:​

resources: [
    { id: 'r1', title: 'Mike' },
    { id: 'r2', title: 'Linda' },
    // ...
]

Mobiscroll Timeline view/ Scheduler – resource definition:​

resources: [
    { id: 'r1', name: 'Mike' },
    { id: 'r2', name: 'Linda' },
    // ...
]

Both FullCalendar and Mobiscroll use similar structures for defining resources, typically including an id and a label-like field. In FullCalendar this is usually title, while in Mobiscroll it is usually name in the resources array. Like FullCalendar's resource objects, Mobiscroll also supports a wide range of additional properties, as demonstrated in this example.

For more advanced use cases, refer to the Mobiscroll documentation for additional options, including custom rendering and templating of resources. You can also explore our demo page for detailed resource configuration examples.

Compared to FullCalendar, Mobiscroll provides a more resource-focused user experience, including features such as fixed rows, reordering, and external drag-and-drop.

Event migration​

FullCalendar defines an event inside the events option using explicit start and end values, together with fields like title, allDay, and extendedProps. Mobiscroll uses the data option and explicit start and end properties for defining the event period.

Event structure comparison​

FullCalendar:​

events: [
    {
        id: 1,
        resourceId: 'r1',
        start: '2017-01-01T10:00:00',
        end: '2017-01-01T12:00:00',
        title: 'Click me'
    }
]

Mobiscroll:​

data: [
    {
        id: 1,
        resource: 'r1',
        start: '2017-01-01T10:00',
        end: '2017-01-01T12:00',
        title: 'Click me'
    }
]

Converting FullCalendar events to Mobiscroll format​

Here’s a simple example of how to convert FullCalendar-style events into the format used by Mobiscroll:

const mobiscrollEvents = fullcalendarEvents.map((event) => {
  return {
    ...event,
    resource: event.resourceId,
  };
});

Every project may have its own unique data format and requirements, so this script serves only as a basic starting point. You’ll likely need to adapt your transformation logic to fit your application’s specific needs.

Loading and saving data​

When selecting a scheduling or calendar UI component, one of the most important factors to evaluate is how the component loads and saves data. The chosen approach can significantly influence performance, scalability, and integration complexity.

We will examine how each framework handles:

  • Loading data from local or remote sources.
  • Saving or synchronizing changes to a backend system.

Loading data​

FullCalendar:

  • FullCalendar accepts local arrays through the events option.
  • It can also load data from JSON feeds or from an events callback function, which receives the visible date range and lets you fetch only the events needed for the current view.
  • If needed, you can refresh remote sources programmatically with refetchEvents().

Mobiscroll:

Let’s see an example for each case:

Local data​

FullCalendar:​

You can use the events option for passing the data inline.

events: [
    {
        id: 1,
        resourceId: 'r1',
        start: '2017-01-01T10:00:00',
        end: '2017-01-01T12:00:00',
        title: 'Click me'
    }
]

Mobiscroll:​

Pass the event array to the data option.

data: [
    {
        id: 1,
        resource: 'r1',
        start: '2017-01-01T10:00',
        end: '2017-01-01T12:00',
        title: 'Click me'
    }
]

Remote data​

FullCalendar​

FullCalendar can fetch remote data through the events callback. The callback receives the currently visible date range, which makes it suitable for loading only the events that belong to the active view.

const calendar = new Calendar(container, {
  plugins: [timeGridPlugin],
  initialView: 'timeGridWeek',
  events: 'https://fullcalendar.io/api/demo-feeds/events.json?with-resources=2'
});

Mobiscroll​

You can load the data through an external request and use the setEvents method to update the event calendar with the newly received data.

In case of Mobiscroll, you can also use the onPageLoading pevent to load the data (on demand) relevant to the currently active view. The event fires every time the date range of the view changes, for example, when someone navigates the event calendar. Getting the events in real time as the user interacts with the UI improves load performance and always serves the most recent data.

mobiscroll.eventcalendar('#myDiv', {
  view: {
    schedule: { type: 'day' }
  },
  onPageLoading: function(args, inst) {
    const year = args.month.getFullYear();
    const month = args.month.getMonth();
    const day = args.month.getDate();

    mobiscroll.getJson(
      'https://example.remotedata.com/weeklyevents/?year=' + year + '&month=' + month + '&day=' + day,
      (data) => {
        inst.setEvents(data);
      },
      'jsonp'
    );
  }
});

In case of the Timeline view, data can also be loaded dynamically during scrolling. Scrolling vertically or horizontally triggers the onVirtualLoading lifecycle event, which can be used to load data incrementally during scrolling.

Saving data​

FullCalendar​

  • Persistence is managed by listening to FullCalendar’s lifecycle callbacks and send changes to your API.
  • Typical hooks include eventAdd, eventChange, and eventRemove.
  • This gives you full control over how changes are saved, but the data layer must be implemented by your application.

Example:

const calendar = new Calendar(container, {
  plugins: [interactionPlugin, timeGridPlugin],
  initialView: 'timeGridWeek',

  events: {events},

  eventAdd: {async ({ event }) => {
      await fetch('/api/events', {
          method: 'POST',
          headers: { 'Content-Type': 'application/json' },
          body: JSON.stringify(event.toPlainObject())
      });
  }}, 

  eventChange: {async ({ event }) => {
      await fetch(`/api/events/${event.id}`, {
          method: 'PUT',
          headers: { 'Content-Type': 'application/json' },
          body: JSON.stringify(event.toPlainObject())
      });
  }},
  
  eventRemove: {async ({ event }) => {
      await fetch(`/api/events/${event.id}`, {
          method: 'DELETE'
      });
  }}
});

Mobiscroll​

  • Persistence is managed by listening to Mobiscroll’s CRUD lifecycle events.
  • To overwrite all events with a new set of data on the event calendar, you can use the setEvents method.
  • The Event Calendar exposes a variety of events that are triggered on certain actions made on calendar events. These events can be used to send your data to your API or save it to persistent storage.

Example for saving, updating, and deleting an event through an API:

mobiscroll.eventcalendar('#myDiv', {
    view: { schedule: { type: "week" } },
    data: [
      { id: 'id1' start: '2023-09-24', end: '2023-09-30', title: 'Short trip!'},
    ],

    onEventCreated: function (args, inst) {
      fetch('add.php', {
          method: 'POST',
          headers: { 'Content-Type': 'application/json' },
          body: JSON.stringify(args.event)
      });
    },

    onEventUpdated: function (args, inst) {
      fetch('update.php', {
          method: 'POST',
          headers: { 'Content-Type': 'application/json' },
          body: JSON.stringify(args.event)
      });
    },

    onEventDeleted: function (args, inst) {
      fetch('delete.php', {
          method: 'POST',
          headers: { 'Content-Type': 'application/json' },
          body: JSON.stringify(args.event)
      });
    }
});

Mobiscroll offers a flexible, event-driven approach suitable for both lightweight client-side setups and API-driven applications. Developers are responsible for implementing their own persistence logic, allowing for high adaptability but requiring more manual integration effort.

Both libraries are capable of handling modern scheduling needs, but the choice depends largely on application scale, data complexity, and desired control over the persistence layer.

Lifecycle events​

Both libraries, FullCalendar and Mobiscroll, provide a comprehensive set of lifecycle event hooks, enabling deep customization and integration with your application logic. These events are emitted at various stages of a component’s lifecycle, offering developers full control to inject custom behavior and extend default functionality.

Whether you’re looking to manipulate data before rendering, respond to user interactions, or perform cleanup tasks, Mobiscroll’s event system offers the flexibility to tailor components to your specific needs.

When migrating between FullCalendar and Mobiscroll, it’s important to note that most lifecycle events follow similar patterns across both libraries. This alignment minimizes friction during the transition process and helps preserve custom behaviors with minimal adjustments.

One such example is how each library handles event updates. Below is a comparison of the respective event handlers and their parameters.

FullCalendar​

In FullCalendar, the eventChange callback is triggered after an event has been modified, for example after a drag, resize, or programmatic update. The callback provides access to the updated event, the previous version, related events, and a revert function.

Example:

const calendar = new Calendar(container, {
  plugins: [interactionPlugin, timeGridPlugin],
  initialView: 'timeGridWeek',
  editable: true,
  events: [events],
  eventChange: {(changeInfo) => {
      console.log('Event changed:', changeInfo.event);
      // changeInfo.oldEvent contains the previous state
      // changeInfo.revert() can be used if saving fails
  }}
});

Mobiscroll​

Mobiscroll components (e.g., Event Calendar, Scheduler, Timeline) expose a similar onEventUpdated event, which is fired when an event is edited. It includes contextual information that allows for granular control over the interaction.

Example:

mobiscroll.eventcalendar('#container', {
    // ...other options...
    data: events,
    onEventUpdated: function (args, inst) {
        console.log('Event updated:', args.event);
    }
});

Although the naming conventions and parameter structures differ slightly between FullCalendar and Mobiscroll, the overall event purpose and customization potential remain aligned. Developers familiar with FullCalendar’s event model will find it straightforward to adapt similar functionality in Mobiscroll, ensuring a smooth migration path with minimal overhead.

To explore the full list of available Mobiscroll lifecycle events and understand how they can be leveraged, please refer to the documentation.

Additionally, you can see these events in action through live, interactive examples for the following Mobiscroll components:

These examples provide hands-on insights into how lifecycle events work in practice.

Feature migration​

As a final step, let’s explore how core features from FullCalendar can be replicated using Mobiscroll. While some capabilities are available out of the box in FullCalendar, Mobiscroll often requires more explicit setup but offers much more flexibility across touch and desktop interactions.

Drag & Drop functionality​

  • In FullCalendar, drag-and-drop editing is enabled with editable: true. To support date clicking, selection, and advanced interactions, the interaction plugin is commonly added as well.
  • In Mobiscroll, the D&D features must be enabled explicitly via configuration options.

FullCalendar:​

const calendar = new Calendar(container, {
  plugins: [interactionPlugin, timeGridPlugin],
  initialView: 'timeGridWeek',
  editable: true
});

Mobiscroll:​

mobiscroll.eventcalendar('#container', {
    clickToCreate: true,
    dragToCreate: true,
    dragToMove: true,
    dragToResize: true,
    eventDelete: true
});

This configuration allows users to create, move, resize, and delete events in Mobiscroll.

Switching Views​

  • FullCalendar includes a built-in header toolbar. You can switch between views by declaring them in headerToolbar. An object can be supplied with properties start/center/end or left/center/right. These properties contain strings with comma/space separated values. Values separated by a comma will be displayed adjacently. Values separated by a space will be displayed with a small gap in between.
  • Mobiscroll doesn’t include a built-in view-switching UI by default. However, it offers greater flexibility by allowing you to implement a custom header where you can design the view-switching experience to fit your needs. For example, you can use a dropdown menu or segmented controls to let users switch between views like Calendar, Scheduler, Agenda, or any other layout that fits your use case.

FullCalendar:​

const calendar = new Calendar(container, {
  plugins: [dayGridPlugin, timeGridPlugin, listPlugin],
  initialView: 'timeGridWeek',
  initialDate: '2020-09-12',
  headerToolbar:{{
    left: 'title',
    center: 'dayGridMonth,timeGridWeek,timeGridDay,listWeek',
    right: 'prev,today,next'
  }}
});

Mobiscroll:​

In Mobiscroll, switching between views like Day, Week, or Month requires setting up a custom header along with event listeners to handle the view changes. You can see an example of this implementation here.

var calendar = mobiscroll.eventcalendar('#container', {

  view: {
    calendar: {
      labels: true,
    },
  },
  defaultSelectedDate: '2020-09-12', // if you want to set the initial view to a specific date

  renderHeader: function () {
    return (
      '<div mbsc-calendar-nav class="cal-header-nav"></div>' +
      '<div class="cal-header-picker">' +
      '<label>Year<input mbsc-segmented type="radio" name="view" value="year" class="md-view-change"></label>' +
      '<label>Month<input mbsc-segmented type="radio" name="view" value="month" class="md-view-change" checked></label>' +
      '<label>Week<input mbsc-segmented type="radio" name="view" value="week" class="md-view-change"></label>' +
      '<label>Day<input mbsc-segmented type="radio" name="view" value="day" class="md-view-change"></label>' +
      '<label>Agenda<input mbsc-segmented type="radio" name="view" value="agenda" class="md-view-change"></label>' +
      '</div>' +
      '<div mbsc-calendar-prev class="cal-header-prev"></div>' +
      '<div mbsc-calendar-today class="cal-header-today"></div>' +
      '<div mbsc-calendar-next class="cal-header-next"></div>'
    );
  },
});

document.querySelectorAll('.md-view-change').forEach(function (elm) {
  elm.addEventListener('change', function (ev) {
    switch (ev.target.value) {
      case 'year':
        calendar.setOptions({
          view: {
            calendar: { type: 'year' },
          },
        });
        break;
      case 'month':
        calendar.setOptions({
          view: {
            calendar: {
              labels: true,
            },
          },
        });
        break;
      case 'week':
        calendar.setOptions({
          view: {
            schedule: { type: 'week' },
          },
        });
        break;
      case 'day':
        calendar.setOptions({
          view: {
            schedule: { type: 'day' },
          },
        });
        break;
      case 'agenda':
        calendar.setOptions({
          view: {
            calendar: { type: 'week' },
            agenda: { type: 'week' },
          },
        });
        break;
    }
  });

});

Timezones​

Handling time zones accurately is crucial in calendar and scheduling applications, especially when working across regions or coordinating international events. Both FullCalendar and Mobiscroll offer support for working with time zones, though they approach it differently in terms of configuration and underlying technology. So, let’s see a simple example of how this scenario is handled in the case of FullCalendar and Mobiscroll.

FullCalendar​

FullCalendar supports local, UTC, and named time zones through the timeZone option. Using UTC ensures consistent cross-browser display. Named time zones are also supported, but depending on the setup they may require a timezone implementation.

const calendar = new Calendar(container, {
  plugins: [timeGridPlugin],
  initialView: 'timeGridWeek',
  timeZone: 'UTC',
  events: {[
      {
          id: '1',
          title: 'Meeting',
          start: '2025-08-27T09:00:00Z',
          end: '2025-08-27T11:00:00Z'
      }
  ]}
});

Mobiscroll​

By default, Mobiscroll will not do any timezone conversion, will display the dates without modification, handling them as timezone-less. If your use case requires interpreting or displaying data in a different time zone, you can achieve this by using one of the supported third-party libraries for time zone conversion:

Mobiscroll exposes two configuration options to handle time zones:

  • dataTimezone option – the time zone in which your event data is stored (e.g., 'utc')
  • displayTimezone option – the time zone in which you want the data to be presented (e.g., 'Europe/Stockholm')

So, let’s say you want to use the Day.js timezone library. After installing it into your project, you can pass the dayjsTimezone object to the Timeline’s timezonePlugin option:

import { eventcalendar, dayjsTimezone } from '@mobiscroll/javascript';
import dayjs from 'dayjs';
import timezone from 'dayjs/plugin/timezone';
import utc from 'dayjs/plugin/utc';

dayjs.extend(utc);
dayjs.extend(timezone);
dayjsTimezone.dayjs = dayjs;

eventcalendar('#myDiv', {
  timezonePlugin: dayjsTimezone,
  dataTimezone: "utc",
  displayTimezone: "Europe/Stockholm",
});

Also, feel free to explore live examples to see how time zones work in action:

Or you can also check advanced demos such as:

You can also store the timezone inside the event data, using the timezone property.

Conclusion​

FullCalendar offers a familiar plugin-based API and built-in toolbar-based navigation, while Mobiscroll provides a more unified scheduling product line with highly configurable scheduler and timeline experiences:

In addition to drag & drop and custom view-switching, Mobiscroll also supports timezone handling and zooming levels. All of our views work seamlessly across both mobile and desktop environments, with full support for touch interactions.

As mentioned above, with some additional setup, most —if not all— features can be effectively replicated when migrating from FullCalendar to Mobiscroll. If you have any specific questions or run into any issues, don’t hesitate to reach out — we’re happy to help.

Templating and renderers​

Event templating​

FullCalendar​

FullCalendar customizes events through event render hooks. The most commonly used option is eventContent, which lets you inject custom markup into the event body. You can also use eventClassNames, eventDidMount, and eventWillUnmount for styling and lifecycle control.

const calendar = new Calendar(container, {
  plugins: [timeGridPlugin],
  initialView: 'timeGridWeek',
  events: {[
      {
          id: '10',
          title: 'Custom Meeting',
          start: '2025-08-27T09:00:00',
          end: '2025-08-27T11:00:00',
          extendedProps: {
              location: 'Room 203'
          }
      }
  ]},
  eventContent: {(info) => (
      <div style={{ background: '#a8d8ea', borderRadius: '4px', padding: '4px' }}>
          <strong>{info.event.title}</strong>
          <div style={{ fontSize: '12px', color: '#444' }}>
              Location: {info.event.extendedProps.location}
          </div>
      </div>
  )}
});

Mobiscroll​

You can customize many parts of the Event Calendar by writing custom templates. In the context of plain javascript these templates are functions that return a string containing the html markup. You will find a comprehensive list of all the available render functions for the Event Calendar in the API templates section.

When you want to customize how the events look, depending on what your goal is, you have two options:

  • Customize the event content - Mobiscroll takes care of rendering the events in the correct order and also prints basic fields, like start/end, whether it is an allDay event or not and also takes care of coloring the event appropriately. Everything else comes from the custom template.
  • Customize the full event - Mobiscroll takes care of rendering the events in the correct order, but everything else comes form the template you write.

To define a custom template, pass a functional to the appropriate option that returns the desired html:

mobiscroll.eventcalendar('#container', {
    // ...other config...

  data: [ { id: 10, resourceId: 1, title: 'Custom Meeting', start: '2025-08-27 09:00', end: '2025-08-27 11:00' }],

  renderScheduleEvent: function (eventRecord) {
    return `
        <div style="background:#a8d8ea; border-radius:4px; padding:4px;">
            <strong>${eventRecord.title}</strong>
            <div style="font-size:12px; color:#444;">Location: ${eventRecord.location} </div>
        </div>
    `;
  }
});

Feel free to explore live examples to see how event content templating work in action:

Feel free to explore live examples to see how full event templating work in action:

Resource templating​

FullCalendar​

In FullCalendar, there are two common approaches for customizing the resource area:

const calendar = new Calendar(container, {
  plugins: [resourceTimelinePlugin],
  initialView: 'resourceTimelineDay',
  resourceAreaColumns: {[
      { field: 'name', headerContent: 'Name' },
      { field: 'city', headerContent: 'City' }
  ]},
  resources: {[
      { id: '1', title: 'Adam', name: 'Adam', city: 'Washington' },
      { id: '2', title: 'Eva', name: 'Eva', city: 'New York' },
  ]}
});

Mobiscroll​

In the case of Mobiscroll, we take a different approach. We provide various templating options (listed below), which allow you to customize the resources. This is unlike FullCalendar, where customization requires modifying the columns with different renderers.

Scheduler​

Use the renderResource option to customize the resource template of the Scheduler. Customize how the resource headers look and what they show. Utilize properties passed in the resources array. It takes a function that should return the desired markup.

Check out how you can style the resources in this example.

Timeline​

In case of the Timeline view there are three places where you can customize the resource column:

  • Use the renderResource option to customize the resource template of the Timeline. Customize how the resource headers look and what they show. Utilize properties passed in the resources array.
  • Customize the empty cell content above the resource column with the renderResourceHeader option.
  • Or if you want to customize the empty cell content below the resource column you can achieve this with the renderResourceFooter option. This element only renders for the Timeline view, if the renderDayFooter option is present.

Check out how you can style these resource parts in this example.

mobiscroll.eventcalendar('#container', {
  // ... other config ...
  resources: [
    { id: 1, name: 'Adam', city: 'Washington' },
    { id: 2, name: 'Eva', city: 'New York' },
  ],
  renderResourceHeader: function () {
    return (
      '<div class="my-resource-header">' +
      'Name' +
      '</div>' +
      '<div class="my-resource-header">' +
      'City' +
      '</div>'
    );
  },
  renderResource: function (resource) {
    return (
      '<div class="my-resource-cell">' +
      resource.name +
      '</div>' +
      '<div class="my-resource-cell">' +
      resource.city +
      '</div>'
    );
  }
});

Header templating​

FullCalendar​

FullCalendar comes with a built-in toolbar system through headerToolbar and customButtons. You can reorder, hide, or extend the header, but unlike Mobiscroll, you do not fully template the entire header as markup.

const calendar = new Calendar(container, {
  plugins: [dayGridPlugin],
  initialView: 'dayGridMonth',
  customButtons: {{
      myButton: {
          text: 'Today +',
          click: () => console.log('Custom button clicked')
      }
  }},
  headerToolbar: {{
      start: 'title',
      center: '',
      end: 'today prev,next myButton'
  }}
});

Mobiscroll​

The header of the Mobiscroll calendar can be fully customized to one's needs with the use of the renderHeader option.

Here's the list of the built in components of the default header. You can initialize these by putting the attributes on the elements:

  • mbsc-calendar-prev - Previous button component, that navigates to the previous month.
  • mbsc-calendar-next - Next button component, that navigates to the next month.
  • mbsc-calendar-today - Today button component, that navigates to the current date.
  • mbsc-calendar-nav - The title navigation button component, that opens the year/month navigation.

The following example will render the prev and next buttons and a custom title.

var myTitle = 'Awesome title';

mobiscroll.eventcalendar('#container', {
  renderHeader: function () {
    return `
    <button mbsc-calendar-prev></button>
    <button mbsc-calendar-next></button>
    <button class="my-custom-title">${myTitle}</button>`;
  },
});

Also, feel free to explore live examples to see how header templating work in action:

Other templating/ renderer options​

Event Calendar​

  • Date header templating - There are two approaches you can take:
    • Customize the date headers of the Event Calendar with the renderDay option by adding relevant content, labels or completely change how they look.
    • If you are looking to customize only the content and don't want to bother with the styling of the event, you can use the renderDayContent option.

Scheduler​

  • Date header templating - There are two approaches you can take:

    • Customize the date headers of the Scheduler with the renderDay option by adding relevant content, labels or completely change how they look.
    • If you are looking to customize only the content and don't want to bother with the styling of the event, you can use the renderDayContent option.

    Check out how you can style the date header in this example.

Timeline​

  • Templating the sidebar header and footer - Besides the resource template, an additional sidebar can be rendered on the opposite end of the row and there are three approaches you can take:

    • Use the renderSidebar option to render a custom sidebar on the right side of the Timeline.
    • Customize the empty cell content above the sidebar column with the renderSidebarHeader option.
    • Or if you want to customize the empty cell content below the sidebar column you can achieve this with the renderSidebarFooter option.

    Check out how you can style the sidebar parts in this example.

  • Date header and footer templating - The headers hold key information like the date, day of the week and in some cases it also holds the full date. Whenever you need to show extra information, or if you would like to change the styling or date format, time format you can use the various header templates, depending on the view configuration. You can also show a footer element, for displaying more information.

    Check out how you can style the date header and footer in this example.

  • Slots - Use the renderSlot option to customize the slot template of the Timeline view.

    Check out how you can style the slots in this example.

  • Variable event height - When using event templating, you might end up with various event heights, depending on the displayed content, e.g. larger description, list of tasks, etc. You can enable support for variable event heights by setting the eventHeight: 'variable' property for the timeline inside the view option.

    Check out how you can set and style the variable event height in this example.

Agenda​

Localization​

FullCalendar​

FullCalendar supports localization through the locale options. These affect button text, month and weekday names, date formatting, week calculations, and the first day of the week.

import frLocale from '@fullcalendar/core/locales/fr';

const calendar = new Calendar(container, {
  plugins: [dayGridPlugin],
  initialView: 'dayGridMonth',
  locale: frLocale
});

Mobiscroll​

Mobiscroll enables localization by letting developers set language, date, and time formats both globally (across the entire application) and locally (on individual components). Highlights:

  • Global settings object lets developers set locale, theme, and format across the app (first example).
  • Each component (e.g., Date Picker, Event Calendar) supports locale switching and custom translations with simple configuration (second example).
  • RTL and calendar system support (Gregorian, Jalali, Hijri)
  • Quick override ability for localized formats ensures that adaptations can be made case-by-case or via global settings.

Example setting the locale option globally:

mobiscroll.setOptions({
    // ...other config...
    locale: mobiscroll.localeFr // French locale applied globally
});

Example setting the locale at the component level:

mobiscroll.eventcalendar('#container', {
    // ...other config...
    locale: mobiscroll.localeFr, // Switch to French locale
});

Conclusion​

For teams building customer-facing schedulers—whether for appointments, reservations, healthcare, or mobile apps—Mobiscroll offers a faster, more reliable path to production. It combines a complete feature set with strong performance and specialized UX capabilities like fixed resources and multi-calendar support. Instead of navigating plugin choices and relying on community-driven solutions like FullCalendar, you get enterprise-ready tools, WCAG compliance, and native components that work seamlessly out of the box—backed by dedicated support.

The overall migration process includes:

  • Adjusting initialization patterns
  • Adapting view configurations
  • Mapping resources and events to Mobiscroll’s structure
  • Enabling features like drag-and-drop manually

With a clear understanding of both libraries’ capabilities and structures, you can migrate efficiently and take full advantage of Mobiscroll’s modern UI and feature-rich environment.

Considering migrating from FullCalendar to Mobiscroll?​

Schedule a call and let's chat about how we can help. We're here to support you in the migration process.