Watch for back-end performance problems. When an app runs slowly, everyone is quick to blame the client-side mobile developer. Yet often the answer lies deep within the technology stack supplying data to the app. When creating new (or modifying existing) services for an app, start with a stubbed-out version that responds immediately with fixed, non-computed data. Set a performance guideline based on this use case, and monitor transaction times during the course of development. Alternatively, some teams we interviewed proactively injected long delays in back-end APIs during test runs to ensure their front-end could handle those delays appropriately. Tools are available to monitor these “full-stack” traces as well, such as Nastel jKool.
Read the Report