Mobile Development Strategy

[Former Member]

Iu2019m confused with some of the surrounding technologies for the development of mobile applications. For a mobile application I am working on, I have exposed a u201Cbapiu201D as a web service through ICF. I can consume the web service in my mobile application. The intended audience for the application would be licensed u201Cprofessionalu201D (named) users so I assume licensing should not be a problem.

The question, what role and why do I concern myself with the following when developing mobile applications?

Mobile Infrastructure, Gateway, SUP (Sybase unwired platform), PI(XI), .Net Connector (NCo) 3.0.

[Former Member · Accepted solution]

Hello Russ,

When you are creating a simple application (no big data transactions and less user), it could be feasible to use the way as you said.

But when there is need for the following, we need such infrastructure to manage applications.

1. dynamic data distribution

2. multiple mobile platform support

3. trusted and reliable data flow.

4. data conflict detection

and many more.

You can find more info about the the insfrastructure architecture here

http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/e0c9feea-935e-2e10-a997-c1baec36f...

Thanks, Senti