APK or IPA size alone does not measure protection overhead. Startup time, transaction latency, memory, battery use and error rates all affect the user experience.
Evaluation approach
Compare protected and baseline builds under the same device, data and network conditions. Record high-percentile latency as well as averages.
Application example
Measure cold startup on a low-powered Android device separately from returning to the foreground on iOS.
Limits and considerations
A brief test on one device does not represent a broad user population. Read results alongside the device and version matrix.
A measurement plan beyond averages
A short average delay can conceal a small number of slow operations that disrupt the user journey. Measure startup, sensitive-operation latency, memory and battery use through separate experiments. Warm execution and cold startup need distinct records.
Compare protected and baseline releases with matching device, network and data conditions. Examine distributions by device segment. A demonstration on one flagship phone does not provide sufficient evidence for low-memory or older devices.
Checks and decisions
- Include low-powered devices
- Separate transaction latency
- Monitor crashes and ANRs
Sources
The primary references above provide the technical basis. Example workflows and evaluation suggestions are this publication’s explanations, not independent test results for a particular product.