You get intrigued and start to interact with the schedules. Every time you want to add or edit an event a user-friendly dialogue appears that lets you quickly type in all information about the appointment including reminder and recurrence. You notice you can filter appointments based on a variety of criteria. You quickly shift appointments with a simple drag and drop and navigate seamlessly between days, months and calendar views.
You start to go deeper into the component and decide to customize one of the samples that mostly resembles the functionality you are looking for. You look at the source code, which is all neat and easy to understand, and quickly see how the API is structured. You need to put restrictions on the new appointments that the user will create. You open the documentation and are pleased to see several topics on event handling that also reference the classes, which provide data and events for the schedule.
Your calendar now has the features you need, built in just a few hours. You are thrilled by the fact! It doesn’t match quite well the styling of the web page where you intend to place the scheduler. Never mind, you quickly check that the styling is made through CSS themes, which are so easy to edit. You replace the colors in the default calendar theme and voilà! You have the schedule you want, ready to be shipped, in a fraction of the time you thought it would take.