v7.3.0
SupportExamplesFree Trial

Getting Started with Bryntum Scheduler Pro in Ionic

Using an AI coding assistant? Install the Bryntum MCP server to give it access to version-specific Bryntum documentation.

Try Ionic demos

Bryntum Scheduler Pro is delivered with a variety of Ionic demo applications showing its functionality. All demo applications have been verified to be compatible with Node.js 20.

View online Ionic demosBuild and run Ionic demos

Version requirements

Minimum supported:

  • Angular: 9.0.0 or higher
  • TypeScript: 3.6.0 or higher (for TypeScript application)
  • Vite 4.0.0 or higher (for application build with Vite)

Recommended:

  • Angular: 12.0.0 or higher
  • TypeScript: 4.0.0 or higher (for TypeScript application)
  • Vite 5.0.0 or higher (for application build with Vite)

Create Ionic application

To get started, the broad steps are as follows:

  1. Access to npm registry
  2. Create Application
  3. Install component
  4. Add component to Application
  5. Apply styles
  6. Run the application

The application we are about to build together is pretty simple, and will look like the illustration below:

Access to npm registry

You can try out Bryntum components for free using our public Bryntum trial packages. If you have a Bryntum license, please refer to our Npm Repository Guide to access the private Bryntum repository.

Create Application

Similarly to all the examples shipped with the distribution, we will be using Ionic CLI to build Ionic applications.

Type the following command to install Ionic CLI:

npm install -g @ionic/cli

We will then create a basic application with Ionic CLI:

ionic start IonicApp blank --type=angular

Here we are using blank, the most simple starter template for the app.

Ionic can use Angular, React, or Vue. By choosing --type=angular, we tell Ionic CLI to generate an application using Angular.

Feel free to select other defaults if needed following instruction provided in the Ionic Framework Documentation

Please feel free to change IonicApp to your preferred application name

You can then move to your application folder

cd IonicApp

Install component

From your terminal, update project dependencies using the following commands:

Trial versionLicensed version
npm install @bryntum/schedulerpro@npm:@bryntum/schedulerpro-trial@7.3.0 @bryntum/schedulerpro-angular@7.3.0
npm install @bryntum/schedulerpro@7.3.0 @bryntum/schedulerpro-angular@7.3.0
If you're using the licensed Bryntum version, ensure that you have configured your npm properly to get access to the Bryntum packages. If not, refer to this guide.

Add component to Application

Edit the src/app/home/home.module.ts file and add the following:

import { BryntumSchedulerProModule } from '@bryntum/schedulerpro-angular';

@NgModule({
    imports : [
        BryntumSchedulerProModule
    ]
})

Then, edit the src/app/home/home.page.ts file and replace the content with the following:

import { Component, ViewChild} from '@angular/core';
import { BryntumSchedulerProComponent, BryntumSchedulerProProjectModelComponent } from '@bryntum/schedulerpro-angular';
import { schedulerProProps, projectProps } from './home.config';

@Component({
  selector: 'app-home',
  templateUrl: 'home.page.html',
  styleUrls: ['home.page.scss'],
  standalone: false,
})
export class HomePage {

    schedulerProProps = schedulerProProps;
    projectProps = projectProps;

    @ViewChild('schedulerpro') schedulerProComponent!: BryntumSchedulerProComponent;
    @ViewChild('project') projectComponent!: BryntumSchedulerProProjectModelComponent;

}

In the code sample above:

  • A simple project is created with a few resources and linked events.
  • Assignments store details on which resources are assigned to specific events.
  • Since Event 2 lacks a start date, the scheduling engine calculates it based on the start date and duration of Event 1.

Learn more in our guide to displaying data in Bryntum Scheduler Pro.

Add component data

Create a assets/data/data.json file for example data and add the following JSON data to it:

{
  "success": true,
  "resources": {
    "rows": [
      { "id": 1, "name": "Dan Stevenson"     },
      { "id": 2, "name": "Talisha Babin"     },
      { "id": 3, "name": "Michael Chen"      },
      { "id": 4, "name": "Sophia Rodriguez"  },
      { "id": 5, "name": "Arjun Mehta"       }
    ]
  },
  "events": {
    "rows": [
      { "id": 1,  "startDate": "2026-01-01", "duration": 3, "durationUnit": "d", "name": "Project Kickoff"        },
      { "id": 2,  "startDate": "2026-01-04", "duration": 4, "durationUnit": "d", "name": "Requirement Gathering"  },
      { "id": 3,  "startDate": "2026-01-08", "duration": 5, "durationUnit": "d", "name": "UI/UX Design"           },
      { "id": 4,  "startDate": "2026-01-13", "duration": 7, "durationUnit": "d", "name": "Backend Development"    },
      { "id": 5,  "startDate": "2026-01-20", "duration": 6, "durationUnit": "d", "name": "Frontend Development"   },
      { "id": 6,  "startDate": "2026-01-26", "duration": 4, "durationUnit": "d", "name": "API Integration"        },
      { "id": 7,  "startDate": "2026-01-30", "duration": 3, "durationUnit": "d", "name": "Testing & QA"           },
      { "id": 8,  "startDate": "2026-02-02", "duration": 2, "durationUnit": "d", "name": "Client Review"          },
      { "id": 9,  "startDate": "2026-02-04", "duration": 3, "durationUnit": "d", "name": "Bug Fixing"             },
      { "id": 10, "startDate": "2026-02-07", "duration": 2, "durationUnit": "d", "name": "Final Deployment"       }
    ]
  },
  "assignments": {
    "rows": [
      { "event": 1,  "resource": 1 },
      { "event": 2,  "resource": 2 },
      { "event": 3,  "resource": 3 },
      { "event": 4,  "resource": 4 },
      { "event": 5,  "resource": 5 },
      { "event": 6,  "resource": 3 },
      { "event": 7,  "resource": 2 },
      { "event": 8,  "resource": 1 },
      { "event": 9,  "resource": 4 },
      { "event": 10, "resource": 5 }
    ]
  },
  "dependencies": {
    "rows": [
      { "fromEvent": 1, "toEvent": 2  },
      { "fromEvent": 2, "toEvent": 3  },
      { "fromEvent": 3, "toEvent": 4  },
      { "fromEvent": 4, "toEvent": 5  },
      { "fromEvent": 5, "toEvent": 6  },
      { "fromEvent": 6, "toEvent": 7  },
      { "fromEvent": 7, "toEvent": 8  },
      { "fromEvent": 8, "toEvent": 9  },
      { "fromEvent": 9, "toEvent": 10 }
    ]
  }
}

Create a src/app/home/home.config.ts file with the following content:

import { BryntumSchedulerProProps, BryntumSchedulerProProjectModelProps } from '@bryntum/schedulerpro-angular';

export const projectProps: BryntumSchedulerProProjectModelProps = {
    loadUrl : 'assets/data/data.json',
    autoLoad : true
};

export const schedulerProProps: BryntumSchedulerProProps = {
    columns : [
        { text : 'Name', field : 'name', width : 160 }
    ],
    startDate : new Date(2026, 0, 1),
    endDate   : new Date(2026, 1, 10)
};
Note that the startDate and endDate configs passed to schedulerProConfig denote the currently visible timespan.

And finally, edit the src/app/home/home.page.html file and replace the content with the following:

<ion-content [fullscreen] = "true">
    <div id = "container">
        <bryntum-scheduler-pro-project-model
            #project
            [loadUrl] = 'projectProps.loadUrl!'
            [autoLoad] = 'projectProps.autoLoad!'
        ></bryntum-scheduler-pro-project-model>

        <bryntum-scheduler-pro
            #schedulerpro
            [columns] = "schedulerProProps.columns!"
            [startDate] = "schedulerProProps.startDate!"
            [endDate] = "schedulerProProps.endDate!"
            [project] = "project"
        ></bryntum-scheduler-pro>
    </div>
</ion-content>

Apply styles

Stylesheets

The following CSS files are provided with the Bryntum npm packages or in the /build folder of the distribution:

File Contents
schedulerpro.css Structural CSS
svalbard-light.css Svalbard Light theme
svalbard-dark.css Svalbard Dark theme
visby-light.css Visby Light theme
visby-dark.css Visby Dark theme
stockholm-light.css Stockholm Light theme
stockholm-dark.css Stockholm Dark theme
material3-light.css Material3 Light theme
material3-dark.css Material3 Dark theme
fluent2-light.css Fluent2 Light theme
fluent2-dark.css Fluent2 Dark theme
fontawesome/css/fontawesome.css Font Awesome Free base CSS
fontawesome/css/solid.css Font Awesome Free solid icons

You'll need to import the structural CSS and the preferred theme into your project for the Bryntum Scheduler Pro to render correctly, and if you are not replacing the icons used by the component, you will also need to include Font Awesome.

Edit the src/global.scss and add the following:

// FontAwesome is used for icons
@import "~@bryntum/schedulerpro/fontawesome/css/fontawesome.css";
@import "~@bryntum/schedulerpro/fontawesome/css/solid.css";
// Structural CSS
@import "~@bryntum/schedulerpro/schedulerpro.css";
// Bryntum theme of your choice
@import "~@bryntum/schedulerpro/svalbard-light.css";

Sizing the component

By default, the Bryntum Scheduler Pro component is configured to occupy 100% of the parent DOM element with a min-height of 10em.

To display the component at the appropriate size, you can, for example, set parent components to take up the full height of the screen.

In your src/app/home/home.page.scss file, add the following:

#container {
    height : 100vh;
}

There are many other solutions depending on the situation. Feel free to adapt the code above regarding your application layout. For more information on the topic, see this guide Sizing the component.

Run the application

From your terminal:

ionic serve

Your application is now available under http://localhost:8100, and your browser should automatically open it for you.

Troubleshooting

Please refer to this Troubleshooting guide.

What to do next?

Further on integration with Ionic

Do you want to know more about how Bryntum Scheduler Pro integrates with Ionic and starts to customize your application? We provide you with a complete Ionic guide here.

Learn about Data

Bryntum components often use multiple data collections and entities.

For a detailed explanation of how these elements interact, see our guide to displaying data in Bryntum Scheduler Pro.

Contents