Roadmap

Goals

Q2 2026 Objectives

Goal 1: What makes PostHog more tailored to how you actually use it (Driver: Dustin Byrne)

E.g. the default dashboard relies on $pageview events, which doesn’t work well for mobile or backend-only use cases.

What we'll ship:

• Discover where our SDKs and defaults fall short (via dogfooding and conversations with customers)

  • We don't yet have a clear picture of the gaps, step one is understanding what they are and how big the work is, so we can decide whether to focus on them or pick them up incrementally

• Proactive user research

  • Conduct interviews with mobile-heavy and backend-heavy customers
  • Don’t rely only on reactive feedback from unhappy users
  • Run surveys targeting those customers

Goal 2: Agent-friendly SDKs (Driver: Dustin Byrne Manoel Aranda Neto)

As more developers rely on AI agents to integrate PostHog products, our SDKs should be easy for agents to understand, configure, instrument, and extend correctly.

What we'll ship:

• Use insights from the wizard team to understand what users and agents are asking SDKs to do
• Make SDK setup, instrumentation, and extension smooth for AI-assisted workflows
• Reduce the ambiguity in our SDK interfaces, docs, and examples so agents can produce correct implementations more reliably

Goal 3: PostHog libraries vNext (Driver: Ioannis Josephides)

What we'll ship:

• Offline-first / async-first posthog-js (Dustin Byrne)

  • https://github.com/PostHog/posthog-js/issues/2673

• Distributed tracking headers

  • https://github.com/PostHog/posthog/issues/20026
  • Ensure libraries are properly connected end-to-end
  • Add remote config support for JS tracking headers
  • Auto-integrate in backend SDKs (similar to Django wrapper)
    • https://github.com/PostHog/posthog-python/blob/2cac15aa68c34c1fc8a6e436d76bd7c4f7ecca47/posthog/integrations/django.py#L28-L29

• More framework-specific wrappers (Dustin Byrne)

  • Expand support for popular frameworks (e.g. Angular, TBD)

• Mobile session replay (Ioannis Josephides)

  • https://github.com/PostHog/posthog/issues/30889
  • Event-based triggers
    • https://github.com/PostHog/posthog-android/issues/467
    • React Native
  • Minimum duration support
    • https://github.com/PostHog/posthog-android/issues/189
    • Android
    • Flutter
  • macOS support
    • https://github.com/PostHog/posthog-ios/issues/200
    • Ensure compatibility with Flutter and React Native on macOS
  • iOS performance improvements
    • https://github.com/PostHog/posthog-ios/issues/321

• Mobile error tracking (Ioannis Josephides)

  • https://github.com/PostHog/posthog/issues/43012
  • Native support
    • React Native
      • Rename package (current one is session replay specific)
    • iOS improvements
      • Line numbers (likely server-side)
      • Swift error messages (likely requires vendoring PLCrashReporter)
        • https://github.com/PostHog/posthog-ios/issues/522
  • Breadcrumbs
    • Error tracking team to design the approach and coordinate with us on SDK implementation

• Flutter desktop support (Windows/Linux) (Ioannis Josephides)

  • https://github.com/PostHog/posthog-flutter/issues/51

Goal 4: Maintaining the SDKs (Driver: Manoel Aranda Neto)

What we'll ship:

• Complete the SDK test harness and integrate it into CI to ensure consistency across SDKs
  • https://github.com/PostHog/posthog-sdk-test-harness
  • https://github.com/PostHog/posthog/issues/51493
• Take ownership of the SDK rotation
• Align and standardize SDK configuration naming (API token vs API key)
  • https://github.com/PostHog/posthog/issues/48234
• Support and contribute to the new ingestion rate limiting project
  • https://github.com/PostHog/requests-for-comments-internal/pull/1036
• Migrate and consolidate /decide, /flags, and /static/array.js into a unified remote config (/static/token/config)
• Document SDK design guidelines and best practices under the SDK handbook page to help contributors avoid common pitfalls

Goal 5: Logs for Mobile (Driver: Anna Garcia)

What we'll ship:

• Add support for collecting and sending app-side logs
  • Add support for collecting and sending app-side logs from Android
  • Add support for collecting and sending app-side logs from iOS
  • Add support for collecting and sending app-side logs from Flutter
  • Add support for collecting and sending app-side logs from React Native

Handbook

What the Client Libraries team does

• SDKs - the knowledge to level these up are in our team

How to work with the Client Libraries team

Reach out in our Slack channel #team-client-libraries

Feature ownership

You can find out more about the features we own