Mobile Application Performance Monitoring (APM)

Feature request

Based on https://github.com/PostHog/posthog/issues/30227

Describe the solution you'd like

Mobile observability / performance monitoring

• Track app startup speed (cold/warm)
• Detect slow screens renders / sluggish UI
• Measure network request timings and highlight slow endpoints (with grouping)
• Break down performance by device model, OS version, app version, and network conditions
• Automatically link performance data to user, session, and session replay
• Tracing
• Simple profiling insights
• Metrics to track device resource usage

Describe alternatives you've considered

People most likely:

• Use other vendors
• Ignore performance issues until users are loud enough to get noticed

Additional context

Mobile performance issues are often device and network dependent, so it’s hard to reproduce locally.
Linking performance with actual user sessions, replays and events will make debugging much easier.

Questions for the Community:

• Would this be useful to you and your use case?
• Would this replace an existing tool you are already using? If so, which one?
• What specific features regarding tracing, profiling and metrics would you like to see?

Please leave a 👍 or ❤️ reaction on this post to vote for it. You votes and feedback help us prioritize what to work on next!

Debug info

- [ ] PostHog Cloud, Debug information: [please copy/paste from https://us.posthog.com/settings/project-details#variables]
- [ ] PostHog Hobby self-hosted with `docker compose`, version/commit: [please provide]
- [ ] PostHog self-hosted with Kubernetes (deprecated, see [`Sunsetting Kubernetes support`](https://posthog.com/blog/sunsetting-helm-support-posthog)), version/commit: [please provide]

Start by reviewing the linked PostHog issue 30227 and the requested capabilities in this issue, then narrow them into an implementable scope. Done should define and deliver a mobile performance monitoring feature covering agreed startup, rendering, network, tracing, profiling, resource, and session-linking requirements; no source files or tests are identified here.