PostHog / PostHog/posthog

Allow setting a survey to only show up on mobile web, not on mobile native

Open
#41,318 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement feature/libraries feature/mobile feature/surveys
Dominant language
Python
Stars
39.9k
Forks
3.4k
Avg merge
7h 27m
Merged PRs (30d)
222

Description

Feature request

Is your feature request related to a problem?

Currently, I'm able to filter a survey so it only shows up on certain device types, which are Desktop/Tablet/Mobile.

However, if I do not want to have a survey show up on native mobile, there's no clear path.

Describe the solution you'd like

I'd like to differentiate between mobile web (browser / webview) and mobile native, to set a survey to only show on either of these cases.

Describe alternatives you've considered

A workaround is setting a survey to be shown only after an event is captured only on the web (like $pageview).

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]

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No files, tests, or entry points are named. Trace the existing survey device-type filtering, then identify where mobile web and native mobile contexts are distinguished. Done means a survey can target mobile web separately from native mobile while preserving the existing Desktop, Tablet, and Mobile options.

Written by the indexing model from the issue text.

Assessment

Domain
frontend, mobile-dev, web-dev
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.