Choose a research method
FromUsers supports three study types. Pick the method that matches how participants encounter the experience and what evidence you need.
Quick comparison
Section titled “Quick comparison”| Method | Participants use | Best evidence | Distribution |
|---|---|---|---|
| Survey | Respond link (email, Prolific, or share) | Attitudes, preferences, ratings, open feedback | Link, email, Prolific |
| Usability test | Respond link with prototype or URL tasks | Task success, behavior, recordings, first click | Link, email, Prolific |
| In-product survey | Your live site or app with the SDK | Contextual feedback from real users in product | Website targeting and triggers |
All three share pages, sections, logic, variables, branding, translations, endings, and Results Studio. That is why teams can keep one research stack instead of three tools.
Choose a survey when
Section titled “Choose a survey when”- You need structured answers at scale without a prototype.
- You are validating messaging, pricing perceptions, feature priorities, or satisfaction.
- You want screeners, advanced question types, and email or Prolific recruitment.
- You do not need screen recording or task success metrics.
Start with Surveys overview.
Choose a usability test when
Section titled “Choose a usability test when”- You have a Figma, ProtoPie, Adobe XD, uploaded, or URL prototype.
- You need participants to attempt tasks with success criteria.
- You care about first click, five-second impressions, preference, or free exploration.
- You want optional screen and participant (camera and mic) recording with transcription on supported plans.
Coffee covers core survey-style needs with limits. Screen recording, card sort, tree test, MaxDiff, conjoint, file upload, and video or audio response are Pro capabilities. Start with Usability testing overview.
Choose an in-product survey when
Section titled “Choose an in-product survey when”- You can install the FromUsers SDK script on a website.
- Feedback should appear as a modal, banner, embedded block, or toast.
- You need URL targeting, scroll or exit triggers, frequency caps, and quarantine between surveys.
- Participants should respond in context, not from an email link (though a respond link still exists for testing).
There is no npm package. You install a script tag with your API key and website ID. Start with In-product surveys overview.
Decision guide
Section titled “Decision guide”-
Do participants need to use a design or live URL to complete tasks? Yes → usability test. No → continue.
-
Should the survey appear inside your product for real visitors? Yes → in-product survey (if you can install the SDK). No → continue.
-
Do you mainly need questionnaire answers via a link? Yes → survey.
If you are unsure, run a short survey first. You can add a usability test when a prototype is ready, then move recurring questions into an in-product survey after release.
Status and roles (all methods)
Section titled “Status and roles (all methods)”| Status | Use |
|---|---|
| Draft | Building and previewing |
| Live | Collecting responses |
| Paused | Temporary stop |
| Closed | Finished |
Admin and Member roles create and edit studies. Viewer reviews. Workspace Private / Shared and View only / Editable still apply.
Related
Section titled “Related”Common questions
Can I use more than one method for the same product question?
Yes. Many teams run a usability test on a prototype, then a survey for attitudes, then an in-product survey after launch. Shared branding and Results Studio keep analysis consistent.
Which method is fastest to launch?
A short shareable survey is usually fastest. Usability tests need a prototype or URL. In-product surveys need the SDK on your site.
Do all methods share the same builder?
Yes. Pages, logic, translations, branding, and endings work across study types. Interactive tasks and prototype settings are usability-specific. SDK targeting is in-product-specific.