Hello, we are planning a new application and need some guidance.
With the 2013 Q3 release now supporting Bootstrap 3 and responsive (RWD) web design, I have a few questions that I can’t seem to wrap my head around. I'll start by briefly describing the general need.
The application needs to be mobile first with support for desktop. Mobile functionality is various views of data (think something like a Groupon mobile site to set the context) with limited input.
While these views of data will most often be viewed on smartphones and tablets, it must still produce well on laptops and larger desktops. My main concern on the desktop will be all the admin functionality (the CRUD of data). I was planning to use Kendo UI Web (MVC Wrappers) for the admin screens. These DO NOT need to provide functionality at the smaller viewport sizes on smartphones.
This seems like a perfect candidate for RWD. Currently, our prototype is an ASP.net MVC 5 application using Bootstrap 3. While Bootstrap definitely handles the responsive nature very well, I find myself wanting to use the Kendo UI Mobile widgets. For example, while the bootstrap carousel is nice, I really prefer the Kendo Mobile Scrollview widget. I like the feel of the Kendo UI Mobile transitions between views and widgets.
This is where problem starts. While I don't have a lot of experience working with Kendo, I do understand that from a mobile perspective, I'm working with an MVC view or two that essentially contain an application with many views of functionality and data to accomplish the page transitions etc. How does this work as you scale up from a smartphone to a desktop? I can't seem to figure out if what I'm supposed to do is simply wrap the mobile "application" in the Bootstrap 3 grid system (ie: col-lg-8 etc.) on an MVC view page.
I guess what is confusing me is why the distinction between Kendo Web and Kendo Mobile when they are now responsive? And to that point, I see from the demos that the only things that really appear responsive from a widget perspective are the grid and scheduler.
I have looked high and low for a blog or something talking about the overall strategy, but have been unsuccessful.
For clarity, this would be an HTML 5 web application, not a hybrid application through icenium, however, that does send me down another rabbit hole of questions!
Thank you for any guidance.
With the 2013 Q3 release now supporting Bootstrap 3 and responsive (RWD) web design, I have a few questions that I can’t seem to wrap my head around. I'll start by briefly describing the general need.
The application needs to be mobile first with support for desktop. Mobile functionality is various views of data (think something like a Groupon mobile site to set the context) with limited input.
While these views of data will most often be viewed on smartphones and tablets, it must still produce well on laptops and larger desktops. My main concern on the desktop will be all the admin functionality (the CRUD of data). I was planning to use Kendo UI Web (MVC Wrappers) for the admin screens. These DO NOT need to provide functionality at the smaller viewport sizes on smartphones.
This seems like a perfect candidate for RWD. Currently, our prototype is an ASP.net MVC 5 application using Bootstrap 3. While Bootstrap definitely handles the responsive nature very well, I find myself wanting to use the Kendo UI Mobile widgets. For example, while the bootstrap carousel is nice, I really prefer the Kendo Mobile Scrollview widget. I like the feel of the Kendo UI Mobile transitions between views and widgets.
This is where problem starts. While I don't have a lot of experience working with Kendo, I do understand that from a mobile perspective, I'm working with an MVC view or two that essentially contain an application with many views of functionality and data to accomplish the page transitions etc. How does this work as you scale up from a smartphone to a desktop? I can't seem to figure out if what I'm supposed to do is simply wrap the mobile "application" in the Bootstrap 3 grid system (ie: col-lg-8 etc.) on an MVC view page.
I guess what is confusing me is why the distinction between Kendo Web and Kendo Mobile when they are now responsive? And to that point, I see from the demos that the only things that really appear responsive from a widget perspective are the grid and scheduler.
I have looked high and low for a blog or something talking about the overall strategy, but have been unsuccessful.
For clarity, this would be an HTML 5 web application, not a hybrid application through icenium, however, that does send me down another rabbit hole of questions!
Thank you for any guidance.
1 Answer, 1 is accepted
0
Accepted
Hello Richard,
Thank you for contacting us. If I understand you correctly, the most suitable approach for your case would be the adaptive web design. Please take a look at the following article, which outlines the differences between that and the responsive one.
In the Kendo UI world, this would mean serving kendo ui mobile application based interface if a mobile device is detected. Of course, this approach means maintaining two different sets of views, targeting different environments. However, this will allow you to effectively address each environment specifics.
Regards,
Petyo
Telerik
Thank you for contacting us. If I understand you correctly, the most suitable approach for your case would be the adaptive web design. Please take a look at the following article, which outlines the differences between that and the responsive one.
In the Kendo UI world, this would mean serving kendo ui mobile application based interface if a mobile device is detected. Of course, this approach means maintaining two different sets of views, targeting different environments. However, this will allow you to effectively address each environment specifics.
Regards,
Petyo
Telerik
Join us on our journey to create the world's most complete HTML 5 UI Framework - download Kendo UI now!