Pineapple on pizza

No data available

Feature ownership
Members

Roadmap

Recently shipped

Default surveys UI for Android (Jetpack Compose)

Android apps no longer need a custom-built UI to display Surveys. The new posthog-android-surveys-compose module provides a ready-made Jetpack Compose UI. Use it by adding the dependency and setting surveys = true. The core SDK picks it up automatically.

It supports open text, single and multiple choice, NPS, emoji ratings, link questions, and server-driven multi-question branching, with full theming via PostHogDisplaySurveyAppearance.

You can find instructions in the updated Android Surveys installation docs

Goals

🔍 Goal 1: Surveys research & pricing exploration

Why: We're in exploration mode on Surveys. We need to determine the product's future direction by understanding willingness to pay and testing a simpler pricing model.

Who: Lucas Faria, Cory Slater

Talk to customers and explore a new pricing model:

  • Speak with ~10 customers who have consistently created surveys or received responses recently
  • Conduct 1:1 calls throughout the quarter, framed around rethinking the future of the product
  • Explore a flat monthly fee for a set number of responses, with a reduced free tier
  • Explore including branding removal in the paid tier
  • Use research outcomes to decide whether to invest further, change pricing, or sunset the product

ðŸŠķ Goal 2: Surveys MCP & skills

Why: Make Surveys usable from agentic Workflows by exposing it through MCP and skills.

Who: Lucas Faria

Ship Surveys MCP tools and skills so users can create and manage surveys from AI clients. Add it as an Early Access feature so users can opt in and signal interest.

📊 Goal 3: MCP analytics

Why: As MCP usage grows, we want to capture the why behind MCP calls – not just cost/latency – and whether users accomplished their goal.

Who: Lucas Faria

Build bare-bones infrastructure for MCP analytics:

  • Ship an initial version in the PostHog MCP server
  • Capture user context around MCP calls (intent, outcome), not just telemetry
  • Work closely with the analytics and growth teams
  • Potential naming: "MCP Insights" or "MCP Feedback"

Handbook

Slack channel

#team-surveys

Questions about this page? or post a community question.