Sprint May 19 to May 30

[lucasheriques]

Sprint Planning

List of incidents + any action items that haven't been scheduled yet

Team sprint planning

For your team sprint planning copy this template into a comment below for each team.

# Team ___

**Support hero:** ___

## OKR

1. OKR, status (red/yellow/green) and action points if yellow/red

## Retro

<!-- Grab the high and low priority items from last time and add whether that item was completed or not -->
- 

### High priority

-

### Low priority / side quests

-

[lucasheriques]

Team Surveys (WIP)

• Surveys support hero: @marandaneto
• 2 days PTO - @marandaneto @ioannisj

🟢=finished 🟡=in progress 🔴=won't finish ⚪=not started

Retro

Retro - Team Notes

What could've been better

• Partial responses queries caused an incident. Wish I'd worked better to make it easier to rollback with a ff instead of reverting the whole PR @lucasheriques
• Focused a bit on session replay performance on iOS this sprint. Trial and error along with profiling sample apps took time but there’s now an open proposal on the table for a potentially major performance improvement — currently awaiting team feedback. @ioannisj
• Adding support for capturing console logs on iOS ended up being more challenging than anticipated and slowed things down for me. @ioannisj
• Tried a side-quest-first approach this sprint, which kind of backfired. I didn't get back to surveys until later in the sprint, which also required picking up momentum to where I left off. I figure less context switching works better for me, so I'll try the opposite approach this sprint @ioannisj
• I feel I’ve slowed down a bit lately — probably just some signs of burnout creeping in. I’ve booked a couple of days off this sprint to regroup, recharge and spend some time with the fam @ioannisj

What went well

• Console log capture for iOS is now supported for session replay, which is a big win for debugging @ioannisj

Retro - Tasks

High priority

• 🔴 Flutter surveys @ioannisj
  • 🟡 Finish public api for taking control of survey rending logic
    • Almost there, but after finishing with flutter UI, I'll need to come back and wire existing iOS implementation with this public API.
  • 🔴 Finish UI views and UI controls (iOS side)
    • Still working on question type view layouts
• 🔴 Android surveys - release beta version @marandaneto
• 🌴 offsite :P @marandaneto
• 🟡 Answer questions when clicking on the choice instead of next/submit button @lucasheriques
• 🔴 Allow templated strings in survey links @lucasheriques
  • Have to figure out a way to make it work with mobile SDKs or let users know
• ⚪️ Option to show multiple questions within the same view - vertically aligned @lucasheriques
• 🟢 ⚠️ Partial responses
  • Finished all docs and PRs, however it ended up triggering an incident
  • Re-released behind a FF after working on optimizing the queries
  • Released as a beta feature for now. Kept enabled_partial_responses as false by default until I remove it

Mobile replay and Mobile SDKs

• 🔴 Manually start and stop session recordings @marandaneto
  • finish it early next week if not today
• PostHog's Session Replay feature degrades Google services performance @ioannisj
• Respect session replay feature flag after /decide endpoint call - Some investigation around this during the sprint @ioannisj

Low priority / Side quest

• 🟢 Capture logs for recordings @ioannisj
• 🔴 Add before_send support @ioannisj
• 🟢 Use CSS files instead of hardcoded JS strings for styling @lucasheriques
• Support customizing the size of the survey popup the survey editor UI @lucasheriques

Goals

Click to expand quarterly goals

• 🟡 Mobile surveys, Everywhere

  • 🟡 Android
  • 🟡 Flutter

• 🟡 Level up survey analysis

  • ⚪ Global analytics view
  • 🟡 A cleaner, more useful survey responses page
  • ⚪ Be able to see surveys result breakdown by week
  • ⚪ Better results analysis with metric based templates
  • ⚪ Don't calculate NPS score for non-NPS questions
  • ⚪ Extra polish and UX improvements across the board, pair up with the Design team to get some ideas

• ⚪ Survey customization

  • ⚪ Better wait period controls
  • ⚪ Alignment customization here and here
  • ⚪ Inline surveys
  • ⚪ Add icons
  • ⚪ Templated strings
  • ⚪ Single-response submit

• Templates, Templates, Templates

  • ⚪ Save custom templates
  • ⚪ Duplicate surveys across projects/environments
  • ⚪ Add mobile-specific templates
  • ⚪ Explore using AI to create survey templates

• 🟡 Make Key Customers Super Happy

  • 🟡 Be lightning-fast at resolving their issues
  • ⚪ Build a case study with a power user

• Hire a Cracked Product Engineer

  • ⚪ Hire and onboard our next teammate
  • ⚪ Make onboarding smooth and fast so they can hit the ground running

High priority

• Option to show multiple questions within the same view - vertically aligned @lucasheriques
• Save custom templates
• Add a onRenderSurvey handler/delegate in survey configuration for iOS and Flutter. @ioannisj
  • Users can use this to take control of rendering/showing a survey when a survey is activated by conditions
  • The default handler will be the default sdk survey implementation on iOS/Flutter
  • This is used by Flutter SDK to take control of iOS survey display, so we may as well expose it properly
• Finish default Flutter surveys UI @ioannisj
  • Finish view layout of all question types
  • Test and handle keyboard avoidance
  • Handle survey style/appearance

Mobile replay and Mobile SDKs

• Manually start and stop session recordings @marandaneto
  • finish it early next week if not today

Low priority / Side quest

• Explore using AI to create survey template @lucasheriques
• Support customizing the size of the survey popup the survey editor UI @lucasheriques

[pauldambra]

Team All your replay are belong to us

Support hero:
@sortafreel (@pauldambra supporting support)

mostly all in... spring bank holiday in UK

Retro

• offsite 💖
• hackaton was amazing

## what we shipped

• Collections

High priority

• Many of our customers have lots of recordings, but struggle to find the "useful" ones.

  • ➡️ set metrics (KPI) and add them to the dashboard @sortafreel
  • ✅ keep improving summaries with user feedback @sortafreel

• Make it super easy to see what filters have results to watch - "show me, don’t make me figure it out"

  • ✅ show recordings in activity by time in the "figure out what to watch" tab @pauldambra
  • out behind a flag, can start to test

• ✅ watch recordings from where they are @veryayskiy

  • turns out the insight that made us think persons page had lots of traffic was wrong so we punted this
  • finished split of collections and saved filters out to people

Side quests and lower priority

• ➡️ RN - session timeout - stop of recordings (we have it in web) @veryayskiy
• ➡️ Digest email @pauldambra
• better "not found" state for recordings @veryayskiy
  • e.g. TTL passed, or recording might be sampled, etc etc
• ➡️ lazy load session recording in the SDK @pauldambra

OKRs 🟡

1. OKR, status (red/yellow/green) and action points if yellow/red

• ✅ 🚀 Goal 1: Get Alex 2 rocketing 2

  • it's great to have Alex 2 on the team... let's make it a success

• 👩‍🔬 Goal 2: Find the needle in the haystack

  • Many of our customers have lots of recordings, but struggle to find the "useful" ones. We want to test and iterate on a bunch of different ideas to get customers to value faster.
  • Understand the needles that people are looking for using user interviews, data analysis and more
  • Better options for users to watch recordings from where they are (e.g. in funnels or experiments)
  • Some people are scared of filtering, some people have no patience for it - give them ways to avoid it
  • Make it super easy to see what filters have results to watch - "show me, don’t make me figure it out"

#30460

High priority

• Many of our customers have lots of recordings, but struggle to find the "useful" ones.

  • set metrics (KPI) and add them to the dashboard @sortafreel
  • keep improving summaries with user feedback @sortafreel
  • TBC once @sortafreel back from 1 day leave

• Make it super easy to see what filters have results to watch - "show me, don’t make me figure it out"

  • show recordings in activity by time in the "figure out what to watch" tab @pauldambra
  • new filters UI without a modal? @pauldambra
  • Digest email out and sending @pauldambra

• watch recordings from where they are

  • follow up saved filters split from customer feedback https://posthog.slack.com/archives/C03JJKLEC8L/p1747317511025839?thread_ts=1747064771.008009&cid=C03JJKLEC8L @veryayskiy
  • ???

Side quests and lower priority

• RN - session timeout - stop of recordings (we have it in web) @veryayskiy
• better "not found" state for recordings @veryayskiy
  • e.g. TTL passed, or recording might be sampled, etc etc
• lazy load session recording in the SDK @pauldambra

[daibhin]

Team Error Tracking

@daibhin off for most of the sprint
@hpouillot off the first few days

Mid-quarter checkin

✅ Launch with pricing

• Released and charging customers!

🟢 Build advanced features

• Really good progress on rules. Mostly done, need to be tested and released
• Moving onto versioning info

🟢 Product quality

• Tons of UI and performance improvements
• Focusing on integrations with other products next

🟢 Make it easier to integrate

• Improved docs
• Improved structure of JS lite to support edge environments
• Focusing on a NextJS specific package next (very common support topic)

High priority

@hpouillot

• TBD for when you're back

@daibhin

• Reach out to highly engaged customers
• Prep rules for release
  • Custom grouping UI
  • Release internally
  • Write docs

@oliverb123

• Symbol set versioning
  • CLI / Upload context
  • Exception event enrichment

[joshsny]

Team Growth

Support hero: week 1 - @zlwaterfield , week 2 - @joshsny

Q2 Goals

• Installation & SDK experience: Automate the setup of 50% of PostHog installations

  • Setup wizard
    • 🟢 Support more integrations
    • 🟢 Uploading environment variables to common hosting providers
    • 🟢 PR workflow
    • Github action
    • 🟠 Automatic event instrumentation
  • 🟠 Be the default analytics provider for vibe coders
  • 🟠 Be the default option in boilerplates for NextJS, React & React Native
  • 🟠 Improve the onboarding experience for self hosting users

• Make it easier to use multiple products

  • Project homepage: make this a good place to see an overview of all your products
  • Gather common pitfalls from user onboarding calls and replays in each product and remove them

• Launch a creative product experiment once a month!

Retro

@joshsny

• 🟢 Lovable: Meet with their team to discuss integration
• 🔴 Vercel: Create example app for PostHog in Vercel repo and ship the PostHog flags adapter - Vercel are dragging their feet on this PR
• Setup wizard:
  • 🟢 Get it on the homepage
  • 🟢 Ship some improvements based on feedback
  • 🟢 Finish off PR workflow
• 🟢 Automate beta workflow: Send events when users move from one stage to another in a preview beta so that they can be used in Customer.io
• 🔴 Investigate why product intents are not activating for some products - investigated, my logs PR has some funky stuff going on
• 🟢 (Extra) Make a start on OAuth provider flow - made more progress than I thought

@zlwaterfield

• Fully rollout in app cc experiment

Sprint

@joshsny

• AI DX:
  • Enable error tracking by default for the frontend
  • Sync with Danilo on next steps
• MCP server:
  • Move deployment setup into posthog cloud infra / charts
  • Fix authentication issue
  • List on marketplaces
  • Document installation into Claude, ChatGPT, Cursor + Windsurf
  • Add as optional step to all wizard installations
• OAuth Applications:
  • Ship OAuth implementation (without real access) and test in prod
• Remove ability to delete account with a PAT
• Vercel flags provider: Create example app (if they finally merge the adapter PR!)
• Product intents: why are you going wrong?

@zlwaterfield
TBC

Time off: @zlwaterfield - 2 days

[mariusandra]

Team DevEx

Work in progress - will be finalized durning standup later today.

OKR

• 👷 Build the "Product OS"
  • 🟢 New layout and "file-based" project view. Almost done
  • ⚪ Nested nodes within nodes Notion style
  • 🟡 Every product is able to export operations (backend) and widgets (components) => AI, notebooks etc.
  • 🟡 Shortcuts and suggestions
  • ⚪ Permissions
  • ⚪ Keep iterating on shared UI components. Split out Lemon UI and Lemon Components.
• ⏱ Improve dev tooling in PostHog
  • 🟡 Roll out "product folders" for all teams
  • ⚪ Convert E2E tests to playwright
  • ⚪ Tests take 5-10min max
  • ⚪ Standardize dev tooling (vscode, flox, docker, self hosted)

Retro

Last issue

Fixed a lot of project tree feedback, added shortcuts, and had a great offsite in Tulum.

High priority

• Project tree
  • Shortcuts - Drag & drop
  • Shortcuts - suggested
  • Table view - more metadata through manifest.tsx files.
  • Split "project tree" logic into "data" and "instance" logics (better file pickers, etc)
  • All other feedback
• Product folders
  • Document the best practices in a README (structure, migrations, etc)
  • Run python tests standalone
  • Encourage people to start moving products over

Low priority

• Project tree
  • Pinning
  • History / activity log

[jurajmajerik]

Team Experiments

Support

@rodrigoi

OKR's

Retro

Juraj

Anders

Rodrigo

This sprint

Juraj

Anders

Rodrigo

[MichaelKutsch-ph]

Team InfrAllTheFun

Retro:

High priority

• MSK tiered storage success 🥳
• 🟡 SOC2 Audit @danielxnj
• 🟡 make RDS proxy work @danielxnj
• 🟡 Move persons out asap @danielxnj
• 🟡 taking care of single point of failure redis @MichaelKutsch-ph: scaled up, adding tracing now to see what is happening to start untangling this. Added quickwit, jaeger, otel
• 🟡 replace loki with a (managed?) logging - incl SIEM @frankh -> victoria logs
• ✅ RDS switching to new instance types and optimizing sizing @bciaraldi
• 🟡 cross-az costs spiking @bciaraldi

OKR Infra

🏃Improve build times for posthog apps
💽 Splitting RDS
🔒 AWS Account and networking re-work

High priority

• Find fractional CISO @MichaelKutsch-ph
• Pick SIEM solution @MichaelKutsch-ph
• Add tracing so that we can untangle Redis usage @MichaelKutsch-ph @bciaraldi
• Productionize LogHog for team 2 @frankh

Low priority / side quests

✅=finished 🟡=in progress 🔴=won't finish ⚪=not started

[haacked]

Team Fortuitous Launches Avoid Gaffes (FLAGs)

Retro

Theme: Getting `/flags` ready for prime time, making local evaluation more robust.

Last sprint: #31747

What went well

Tulum offsite!

• @haacked

  • Deployed feature flags secure token
  • WASM hackathon - conclusion, not ready for prime time.

• @dmarticus

What could've gone better

• Didn't finish support old /decide fields for flag so rollout for flags is halted for now. That's top priority.
• TODO

This sprint

Theme: Support legacy /decide response fields for /flags, scale up infra to support wide rollout, and roll new flags everywhere; improve local_evaluation.

High Priority

• @dmarticus

  • ???
    Question: What's the status of Behavioral Cohorts?

• @haacked

  • Fix bug in flags paging on the person page
  • Port /local_evaluation to Rust.

Low Priority

• Look into how competitors instrument feature flags
• [ ]

Support

• 05/19 - 05/23: @haacked
• 05/26 - 05/30: @dmarticus

Time Off

@dmarticus on 5/19 - 5/23
@haacked on 05/26 - 5/30

Q2 2025 Objectives

(Details here)

• 🟢 Flag Stability, Consistency, and Resiliency
• ⚪ Behavioral Cohort Targeting
• ⚪ AI IDE Integration