Design Studio vs SAPUI5

Question

This thought has been bothering me and I just want to ask some experts what they think
I was wondering regarding the difference between creating a Dashboard/Application in Design Studio or direct using SAPUI5. I have create some native application using OData and consuming it in a SAPUI5 application using the MVC. I am current facing a requirement to create dashboard application using Design Studio and I am finding it difficult to create the relation between the both if there is such a thing. What I find really difficult is to not have a fool view of the HTML5 and script. Instead I am required to input varies scripts in different section in order to manage the events. Are there any plan to make DS more like a wysiwyg of the SAPUI5 which has a lot more elements and give direct visibility in an editor to manage properties and events. It just feels harder to use DS even though you can drag and drop elements. With SAPUI5  you just go the public SAPUI5 SDK check an UI element snippet code paste and go to the API and start fixing in the way you want.

Answer 1

Hi Carlos,
in the context you describe - access to HANA models in native HANA environment, I am sure you can come quite far also with Native UI5 on top of ODATA. The difference is - in this path you are on your own (which is sometime better, sometimes not so good)...
I know that there is a functionality of generating HANA Views based on BEx Queries, and this is improved in last SPs of 7.40 NW - nevertheless there will be still some restrictions. And this is the place where the difference starts:
BEx Query variable handling - here you would need to code some prompt dialog on your self, which is delivered in design studio
More complex functionality in BEx Queries - I do not know what is the delta, but I know there is some
Hierarchy handling - is HANA already handling all cases of hierarchies, even then - there are small differences in comparison to BW.
Visualization - I am not sure if you can get a real cross-tab component (perhaps you do not need it)
Context Menu - also something you have to make on your own
more others I do not have in my mind now...
Basically this is also the question - is the HANA functional scope for your scenarios comparable and acceptable to those which you are running in WAD? For some customers this answer is YES, for some NO. If yes, you can look at other reporting possibilities (eg. plain UI5). If no, I would recommend to go with Design Studio as many functions which are complex to develop are available already in the framework.
Personally, I am wandering about your WAD scenarios - as very often those are much more complex and bound to BW functionality which is already answering the question above to NO, but perhaps some can be answered to YES.
In practice, I think a mixed solution is a the key - you can try to move to native HANA as much as possible, this brings value - in terms of the stack clarity and also in terms of performance as there is nothing between HANA and UI (almost).
Btw, the statements above are as of TODAY - I am sure in few years those will be revised with new HANA releases and improvements in the HANA models.
this was my private view on this topic.
Karol