Understanding real usage.
WHAT CRASH REPORTING PROVIDES
Reports of crashes with stack traces, device details and frequency.
WHY IT IS ESSENTIAL
Most users never report a crash; they uninstall.
WHAT TO MONITOR
Crash-free session rate New crashes after each release Crashes concentrated on specific devices or versions
WHAT TO DO ABOUT A SPIKE AFTER RELEASE
Establish whether to halt the rollout.
WHAT ANALYTICS PROVIDE
What features are used, by how many, and where people abandon.
WHAT TO MEASURE
Completion of key tasks Where users stop Retention over time
WHY THOSE RATHER THAN SCREEN VIEWS
They answer whether the application works for people.
WHAT TO BE CAREFUL WITH
Collecting more personal data than needed Analytics libraries adding size and data consumption Obligations relating to personal data
WHAT TO DO ABOUT THOSE OBLIGATIONS
Disclose what you collect, obtain consent where required, and honour opt-outs.
Take advice on your position.
WHAT TO AVOID
Tracking that users would object to if they knew.
WHAT TO TEST
That reporting works in release builds.
