Slider question type for surveys
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 39.9k
- Forks
- 3.4k
- Avg merge
- 6h 51m
- Merged PRs (30d)
- 232
Description
Feature request
Is your feature request related to a problem?
I want to be able to have users indicate the price point they'd be willing to pay for our product on surveys.
Describe the solution you'd like
A slider that lets me configure the range and units. In this particular case, I'd like to set the range from $0.01 to $20.00. The user can set the slider to the price they think is right for the product.
Describe alternatives you've considered
We've been using multiple choice but users are selecting the lowest amount every time, which we don't think is representative of what they actually think the right price is. They're likely selecting the lowest number because they'd obviously prefer us to pay a lower price.
Additional context
Thanks for reading this!
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
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue does not name any files, tests, or entry points. Start by locating the existing survey question-type implementation and tracing how question configuration and responses are handled. Done means surveys can configure a slider's range and units, including the requested price range, and respondents can submit a selected value.
Written by the indexing model from the issue text.
Assessment
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100