We all understand how the mobile trends impact the modern web development and how important it is to create web sites and apps that work seamlessly on both desktop and mobile. Every developer wants to produce sites that look good regardless of whether they are accessed via your boss’s laptop, your mother’s tablet or your friend’s smartphone.

ASP.NET Scheduler 

Aiding you in the journey from desktop to cross device

Our goal at Telerik is to create UI tools which:

  • Facilitate the developers’ work
  • Have modern, fast and slick UI
  • Work equally well on your PC, touch screen laptop, tablet or even a smartphone.

Customer feedback suggests that one of the important directions to develop UI for ASP.NET AJAX is support for touch and mobile devices. The Q1 2014 release brings user experience tailored to any device:

  • Page Layout – this control will help you quickly build your page layout on the server side, add responsive capabilities to your sites and apps, and reduce network usage on mobile devices. You never know whether your sites will be displayed on multiple devices, so this control will handle them. Even more, you can easily make your legacy apps responsive on mobile by incorporating the Page Layout control in them.
  • Device Detection Framework – helps you get information about the device screen dimensions of your site’s or app’s users in CSS pixels. It tells you whether the screen is small, medium, large, or extra large, enabling you to serve different content for each.

Classic, Lightweight, Mobile

Even the improved lightweight rendering can fall short of being proper for mobile. That’s why we introduced eponymous mobile render-mode. It’s not just extension of the classic or lightweight rendering; the scripts, styles and rendering are engineered to offer mobile a first-class experience.

Speaking of scripts, styles and rendering, we just can’t not brag about the massive improvements in the mobile rendering of RadScheduler:


Classic (bytes)

Mobile (bytes)

Delta (%)














Choosing the right render mode could be hard, but you can always turn on the RenderMode=”Auto”, which will automatically select the right rendering of the control depending on the device and browser*:

  • Menu - when accessed via a mobile device, the menu changes to create a user experience tailored to the device screen size. In this mode, the control is mobile-friendly and its touch zones are bigger and easier to select.

  • Scheduler - when loaded on a mobile device, the scheduler:
    • Renders the inputs and buttons it contains as native controls. This makes it lighter and better performing and also offers the native for the device experience.
    • Is mobile-friendly and its touch zones are bigger and easier to select.
  • RadTileList - the control offers a responsive rendering that is the same for all resolutions and devices, but its styles and scripts adapt it to the different cases by rearranging, hiding or collapsing its inner elements. You can easily turn on the adaptive and responsive rendering via the RenderMode="Mobile" property or by choosing the “Auto” mode.
  • We also enabled elastic capabilities in Button, Dock, Form Decorator, Image Gallery, Notification, Social Share, ToolTip, Window (more to follow in Q1 2014 SP1). The elastic behavior means that the control will resize proportionately to the font size you have selected for it.

All of the above features are demonstrated in our new tutorial sample application named RWD – responsive web development in ASP.NET. We will be really glad to get your feedback after playing with it and the new render mode.

You can find more information about what’s new in Q1 2014 by checking the Release notes and the What's New pages.

If you like to attend video presentations or you are just curious to see more cool and interesting stuff, don’t miss to join the DevCraft Q1 online conference:

Join the DevCraft Q1 online conference

*We make assumptions.

About the Author

Rumen Jekov

(@Rumen_Jekov) started his career at Telerik’s ASP.NET team in 2004 as a support officer and passed through the position of a Team lead to become a Product Manager. He has answered more than 42,000 tickets helping customers solve their problems. At present, his top goals are to bring full mobile capabilities and lightweight rendering to the AJAX suite as well as to increase the stability and backwards compatibility of the controls. Off work, he enjoys biking, watching movies and reading books.

Related Posts