rubyforgood / rubyforgood/Flaredown
Onboarding: Add acquisition question
Open
Nobody has claimed this yet.
type:feature-request
- Dominant language
- Ruby
- Stars
- 50
- Forks
- 21
- Avg merge
- 6d 12h
- Merged PRs (30d)
- 16
Description
Analytics platforms don't really tell us the whole story about how users found our service. We should consider adding a question during onboarding to learn more about this.
How did you hear about Flaredown?
- Search on google
- Friend/family told me about it
- Facebook post
- Saw it on mobile app store
- Other
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
Start by locating the onboarding flow and the existing handling for user questions or survey responses. Confirm where the selected answer should be stored and displayed, then verify that each listed option can be submitted and retrieved successfully.
Written by the indexing model from the issue text.
Assessment
- Domain
- full-stack
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100