This question is locked. New answers and comments are not allowed.
Daniel Sprague
Top achievements
Rank 1
Rank 1
Daniel Sprague
asked on 07 Nov 2012, 02:19 PM
Hi Guys,
Thanks in advance to all who replied to this.
Need some advice here.
We're wanting to develop a dashboards solution internal to my company. Typical LOB dashboards for management/CEO/Board Directors.
For the most part, everything is windows platform in my company, but lately more and more non-windows devices have been popping up (iPads, iPhones, Blackberries, etc).
In the end, the dashboards need to be accessible on whatever device employees are using.
Because of the Silverlight and Telerik's awesome controls/functionalities, we would like to use Silverlight as the primary tool for people viewing the dashboards on their windows computers. But since Silverlight isn't accessible on iOS, we'll have to use something else, such as ASP/AJAX/HTML5/Kendo there.
So we'll need 2 front ends. Both displaying essentially the same data, in essentially the same manner and same controls (lots of grids, charts, etc.) There will be some exceptions, some things only accessible on full sized computers/monitors, due to screen size limitations.
For the most part, all data will be read-only, merely presenting it. But some exceptions will exist, where users will be able to save items.
What we need advice on is the best way to architecture this. Ideally we won't have 2 completely different applications, but rather the same application, just having 2 different UI's.
Would MVC be best to make this possible? Or MVVM?
Would either of those technologies enable a Silverlight UI and a HTML5/Kendo/Ajax UI to access the middle tier similarly, with only 1 business layer being necessary? Or is there just no way around that, and 2 business layers would be necessary?
Thanks very much for any and all feedback/suggestions!
Daniel Sprague
Thanks in advance to all who replied to this.
Need some advice here.
We're wanting to develop a dashboards solution internal to my company. Typical LOB dashboards for management/CEO/Board Directors.
For the most part, everything is windows platform in my company, but lately more and more non-windows devices have been popping up (iPads, iPhones, Blackberries, etc).
In the end, the dashboards need to be accessible on whatever device employees are using.
Because of the Silverlight and Telerik's awesome controls/functionalities, we would like to use Silverlight as the primary tool for people viewing the dashboards on their windows computers. But since Silverlight isn't accessible on iOS, we'll have to use something else, such as ASP/AJAX/HTML5/Kendo there.
So we'll need 2 front ends. Both displaying essentially the same data, in essentially the same manner and same controls (lots of grids, charts, etc.) There will be some exceptions, some things only accessible on full sized computers/monitors, due to screen size limitations.
For the most part, all data will be read-only, merely presenting it. But some exceptions will exist, where users will be able to save items.
What we need advice on is the best way to architecture this. Ideally we won't have 2 completely different applications, but rather the same application, just having 2 different UI's.
Would MVC be best to make this possible? Or MVVM?
Would either of those technologies enable a Silverlight UI and a HTML5/Kendo/Ajax UI to access the middle tier similarly, with only 1 business layer being necessary? Or is there just no way around that, and 2 business layers would be necessary?
Thanks very much for any and all feedback/suggestions!
Daniel Sprague
2 Answers, 1 is accepted
0
Hello Daniel,
Vlad
the Telerik team
The best approach in my opinion will be to expose services in order to communicate with your data layer. For desktop you can use either Silverlight or WPF while for mobile devices you can use Kendo.
Regards,Vlad
the Telerik team
Explore the entire Telerik portfolio by downloading Telerik DevCraft Ultimate.
0
Daniel Sprague
Top achievements
Rank 1
Rank 1
answered on 07 Nov 2012, 05:46 PM
Thanks Vlad... you make it sound so simple... sure wish it was.