# hanson.wtf a blog? This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## On the Utility of a (User) Session on Mobile DevFeed: [On the Utility of a (User) Session on Mobile]() Original publisher: [Read original article]() Author: Hanson Published: 2025-05-20T05:47:27Z Content type: opinion Language: en Sources: [hanson.wtf]() Topics: [Mobile](), [sessions](), [telemetry](), [session replay](), [Monitoring](), [Processes]() Tags: [android](), [checkout](), [conversion](), [mobile](), [monitoring](), [observability](), [performance](), [session-replay](), [sessions](), [telemetry](), [time](), [ui](), [work]() ### AI overview This commentary explains why mobile telemetry should be organized around user sessions rather than app-process lifetimes or raw time in the app. Sessions group telemetry and actions within a shared usage context, supporting session replay, usage metrics, and analysis of performance, errors, abandonment, and conversion. ### Source excerpt On mobile devices, the lifetime of a process that backs an instance of an app isn't necessarily mapped to its usage lifecycle. Even if you ignore implementation details like Android's process forking and specialization via zygotes, the app process is often already created when a user taps on the app icon to launch the app, [...] ## On the Real Subject of Observability on Mobile DevFeed: [On the Real Subject of Observability on Mobile]() Original publisher: [Read original article]() Author: Hanson Published: 2025-05-11T06:35:40Z Content type: article Language: en Sources: [hanson.wtf]() Topics: [observability](), [Mobile](), [telemetry](), [Monitoring]() Tags: [crash](), [dashboards](), [flexibility](), [metrics](), [mobile](), [monitoring](), [observability](), [performance](), [production](), [telemetry](), [time-series](), [work]() ### AI overview This commentary distinguishes observability from monitoring and argues that mobile observability should support flexible, ad hoc aggregation of production telemetry. It emphasizes connecting performance changes with user behavior and business KPIs, rather than reporting only application-level metrics such as heap size, startup percentiles, or crash rates. ### Source excerpt Lets get something straight. Observability isn't the same as monitoring. Yes, both are powered by telemetry collected from production that are crunched down into metrics, shown as some sort of time-series, graph, or table of numbers. But the key difference is that o11y requires flexibility in aggregation, and on mobile in particular, o11y should give [...] ## Mobile Observability Beyond Crash Tracking and Aggregate Metrics DevFeed: [Mobile Observability Beyond Crash Tracking and Aggregate Metrics]() Original publisher: [Read original article]() Author: Hanson Published: 2024-12-10T07:38:37Z Content type: opinion Language: en Sources: [hanson.wtf]() Topics: [observability](), [Mobile](), [Monitoring](), [telemetry]() Tags: [android](), [app-performance](), [crashes](), [latency](), [metrics](), [mobile](), [monitoring](), [observability](), [performance](), [sdks](), [tech](), [work]() ### AI overview The article argues that basic mobile monitoring, such as crash counts and aggregate performance metrics, does not provide true observability. It advocates actionable production data that helps developers investigate who is affected by issues and why. ### Source excerpt The Observability-Free Zone For most companies, "mobile observability" is a misnomer. I say this because the data that most mobile devs have to "observe" their app in production is laughably simplistic. The vast majority make due with basic crash tracking and precomputed metric aggregates as the only lens into how their app is performing in [...]