Why not simply use
and connect to a Windows Terminal server and use SAPGUI there?
from the experience implementing SAP GUI for Java with as much functionality as possible on the Java platform, it is expected to be a major effort to implement a useful and functional "SAP GUI" for Android or for any other Mobile OS.
Given the very different user experience on mobile device including tablets, the "port" would also not provide the expected user experience. The same result you can achieve by using a remote solution like proposed earlier in this thread.
What would you think about this approach and what would be your requirements?
Looking forward to your feedback.
Has the "Framework" to be installed from the Market/Appstore, or would this be a web based approach like Webdynpro (for ABAP)?
Does programming mean there would be additional classes within the repository like CL_MOBILE_ALV_GRID?
Would it be pure online, or are there any thoughts on local storage?
How would the communication work? Would it be port 32xx based (which would mean devices would have to be integrated into a VPN or something similar)?
the idea is to have the classes to program against (like CL_MOBILE_ALV_GRID) executed on the ABAP runtime of the application server. It would be a pure online scenario with an http connection (potentially using SAP Gateway) between the client running on the mobile device and the application server. On the mobile device the UI controls would be implemented as part of a native app, that would be required to be deployed.
sounds even more interesting.
Since we already thought of an approach like this in our company, and are already starting a project to evaluate use-cases with our customers could you provide information on how far your idea has been already materialized.
thanks for your interest in our idea.
We are in the conceptual phase and still open for requirements. In case discussing the use-cases with your customers reveals some ideas, wishes or requirements for a "SAP GUI for mobile devices", don't hesitate to let us know.
Because the usability of an application which was written for using mouse and keyboard, while you are on a device which lacks both, is simply "not very good" (and these are nice words).
A thick client is able to take the possible input types of the given device into account and therefore would be much better in terms of usability. There are other advantages as well like being able to cache data on the client for a smother response to user interaction. If you take a look at some controls in the SAPGUI like ALVs this is already heavily used. Otherwise every scrolling for example would need client server communication - even if you scroll to a position where you have already been. The SAPGUI for HTML "solves" this by just transferring the entire table at the beginning. Not very nice in terms of response times if you have a big table.
There is another possibility for developing Mobile UI. Using Neptune Application Designer: SAP IDE installed as an AddOn, getting the best from SAP like search helps, parameter ID, conversion exists, dictionary objects etc.
Its possible to see tutorial videos on the following link