Currently we are switching our SAP Mobile Platform (SMP) from Version 2.3 to 3.0. One result of developing for the new platform is that we have to redesign an Approval app built on Hybrid Webcontainer (HWC) using MBOs to a new design using Kapsel and an OData source. While MBOs and the HWC have their pro's and con's the data transmission worked really nice using Workflow DCN and RFC for the connection between SAP and the SMP. And you could use the app also offline due to the cached data.
Redesign for SMP 3.0 in this case means we have to rebuild the whole backend logic and application from scratch. Therefore I am digging me through example code in order to learn about the new programming paradigms.
You can easily experience this by yourself if you build a Workflow Starter Application using the SAP NetWeaver Gateway Productivity Accelerator (GWPA) based on the standard WFSERVICE. Of course this Starter App is only to see as a help to get started and no performance optimization is included there. But still the same mechanism is used in all Gateway Online apps and you cannot rely on good network coverage during daily use.
For my taste an app has to perform always well and I never want to see a Busy Indicator when I use an App. The only exception from this may be some Online transactions like bookings where I need to get a confirmation immediately.
Now what are you thinking about Gateway services and Online apps? Am I giving a theoretical example here because all apps out there are highly optimized or are using fast WiFi connections? Or maybe it does not annoy you if you see these fancy whirling Busy Indicators from time to time on your device? Or is this only a temporary problem until SMP 3.1 will offer Offline OData for Kapsel apps?