Hello,
I know that Web Dynpro for ABAP is not supported by mobile devices. The rendering seems to works, but the dropdown box is not usable on Google Chrome, iPhone or Android. I read here in the forum that avoiding this dropdown is the only solution.
But it won't be the best solution, how knows which user agents future devices will send and then maybe we will see a "Your browser is not supported" like in IE10 for WebDynpro Java...
So I read your suggestions to use BSP, ITS mobile or new technologies like SAPUI5.
Here are my thoughts - any inputs are appreciated:
BSP comes with SAP, and I think it's biggest advantage is to directly code ABAP and re-use some parts of Web Dynpro ABAP - like data selections or function calls. (Maybe some jQuery or CSS can be included to give it a nice look?)
But today I stumbled about one error:
- <htmlb:content>: (*) This browser is not supported; for Design2003 the Internet Explorer as of 5.50 and the Mozilla as of 1.75 are supported
So maybe I should just use plain HTML tags and no HTMLB?
ITS mobile is more about mobile webpage for old phones or scanners - I think there is a fixed layout, so the whole logic needs to be recreated in a dynpro and then the mobile pages have to be generated, but anyway - I can use ABAP.
SAPUI5 is a whole new technology from SAP and it seems this is their future direction for user interface - good approach - device independent and so on. So first step would be "patching up" the system that SAPUI5 can be used. But I can't use ABAP code directly. So no direct "select * from ...". I would need an extra NetWeaver Gateway installation, implement for all my ABAP logic OData services and then I would be able to bind my data to an input element.
So from my point of view, BSP seems here like the winner, because I think I have the most control over the HTML code AND can use ABAP.
But I keep an eye on the Neptune Application designer. It seems more like an ABAP+HTML approach - but didn't get my hands on this up until know.
So what do you think?