Screen Loading
Monitor screen loading performance in your mobile app with Luciq APM. Track how fast screens load, identify slow screens, and optimize user experience.
Last updated
Monitor screen loading performance in your mobile app with Luciq APM. Track how fast screens load, identify slow screens, and optimize user experience.
Luciq automatically captures the time it takes for any UI Kit screen to load. This covers the time for any View Controller between viewDidLoad and viewDidAppear, which includes the following lifecycle methods:
viewDidLoad
viewWillAppear
viewWillLayoutSubviews
viewDidLayoutSubviews
viewDidAppear
Luciq will automatically show spans and operations that occurred during the View Controller loading; these include:
Network Requests
Database Queries
UI Kit Lifecycle methods
You can also define custom points in each View Controller to manually inform the SDK that screen loading has ended.
🚧 Minimum Required SDK Version
SwiftUI Screen Loading is supported starting iOS SDK v14.0.0
To be able to measure the loading time of your SwiftUI views, you need to instrument your views by wrapping them in our LuciqTracedView component:
Luciq will automatically show spans and operations that occurred during the SwiftUI view loading; these include:
Network Requests
Database Queries
The body span, which represents how long the body object took to load
Luciq calculates an Apdex score for your app traces as a way of measuring their performance. An Apdex score ranges between 0 and 1; the higher the value, the better:
Apdex score ≥ 0.94 equates to Excellent performance.
Apdex score ≥ 0.85 and < 0.94 equates to Good performance.
Apdex score ≥ 0.7 and < 0.85 equates to Fair performance.
Apdex score ≥ 0.5 and < 0.7 equates to Poor performance.
Apdex score < 0.5 is considered Unacceptable.
When an app trace occurrence is collected, it is flagged based on a pre-defined target (T). An app trace occurrence is considered:
Satisfying: if its duration ≤ T
Tolerable: if its duration > T and ≤ 4T
Frustrating: if its duration > 4T
Then, based on the bucketing explained above, the Apdex score is calculated as follows:
Total occurrences = Satisfying occurrences + Tolerable occurrences + Frustrating occurrences
Apdex score = (Satisfying occurrences + 0.5 * Tolerable occurrences) / Total occurrences
By default, the target is set to 0.1 seconds; however, you can easily change this number from your dashboard by clicking on your current threshold in the Apdex section.
Last updated