Page 1 of 1
How do you sync API contracts with your team?
Quick survey (~4 min) to understand real pain points in FE–BE collaboration. No sign-up, no spam.
FE / Frontend = web OR mobile, both count!
01 — About You
01 - What's your primary role?
*
01 - What's your primary role?
A
Backend Dev
B
Frontend Dev
C
Fullstack Dev
D
Other
02 - Typical team size when working on a project?
*
02 - Typical team size when working on a project?
A
Just me
B
2–3 people
C
4–10 people
D
10+ people
03 How often do you work in a FE + BE split team?
*
03 How often do you work in a FE + BE split team?
A
Always
B
Often
C
Sometimes
D
Rarely
02 — Current Workflow
04 - How does your team currently define and share API contracts?
*
04 - How does your team currently define and share API contracts?
Postman / Insomnia collections
Swagger / OpenAPI YAML
Notion / Google Docs / Wiki
Chat (WhatsApp, Slack, Discord)
Verbal / no documentation
Other
05 - When does FE usually start building UI components?
*
05 - When does FE usually start building UI components?
A
Before BE starts — we agree on contract first
B
Roughly in parallel — some waiting happens
C
After BE has working endpoints
D
Varies a lot per project
06 - How often does FE end up waiting for BE before they can continue?
*
06 - How often does FE end up waiting for BE before they can continue?
A
Almost always
B
Often
C
Sometimes
D
Rarely
E
Never
07 - When FE does have to wait, roughly how long?
*
07 - When FE does have to wait, roughly how long?
A
Hours
B
1–2 days
C
3–5 days
D
A week or more
03 — Pain Points
08 - Has FE ever built something based on an assumed API shape, only to find out BE returned something different?
*
08 - Has FE ever built something based on an assumed API shape, only to find out BE returned something different?
A
Yes, often
B
Yes, a few times
C
No, never
09 - How painful is the current FE–BE sync process on a typical project?
*
09 - How painful is the current FE–BE sync process on a typical project?
0
1
2
3
4
5
Not painful
Extremely painful
10 - What's your biggest frustration with the current workflow?
04 — Tool Validation
11 - Have you tried any dedicated tool to solve this? (Swagger, Stoplight, etc.)
*
11 - Have you tried any dedicated tool to solve this? (Swagger, Stoplight, etc.)
A
Yes, still using it
B
Yes, but stopped
C
No, but I know they exist
D
No, didn't know
12 - If there was a tool where BE defines the contract and FE instantly gets a live mock server — would that change your workflow?
*
12 - If there was a tool where BE defines the contract and FE instantly gets a live mock server — would that change your workflow?
A
Yes, definitely
B
Probably yes
C
Not sure
D
Probably not
13 - If the tool is fully open source + self-hostable, would you consider using it?
*
13 - If the tool is fully open source + self-hostable, would you consider using it?
A
Yes, open source matters to me
B
Depends on the quality
C
Open source doesn't factor in
14 - Anything else you want to share about your API workflow?
Your responses are anonymous and will only be used to shape a developer tool. No personal data is stored unless you choose to leave contact info.
Submit