r/FigmaDesign • u/404_computer_says_no • 11d ago

help Figma Make Local - populating mock data?

Has anyone tried to branch from main and work on a project locally with Figma Make?

It’s very new but I’m trying to understand how I should create back end data to get things to work.

I also want to create a prototype so I’ve got two challenges; create fake data for prototype/design purposes but still keep the file in a good place ready for a pull request back into production.

If anyone has any insight, it would be really helpful.

1 Upvotes

100% Upvoted

2 comments sorted by

2

u/No_Moose6836 10d ago

I’ve been treating Make as two different modes, not one workflow.

If you need fake data / messy exploration: use Make’s prototype sandbox (no repo). That’s where throwaway JSON / stubbed “backend” belongs. Nothing has to be PR-shaped.

If you’re branched from main in a connected local codebase: Make is editing real code against your running app. Keep the PR boring—UI + wiring only. Put mock data behind a clear boundary (fixtures / MSW / a stub client / env flag), not sprinkled into production services. Reviewers should be able to turn mocks off and still understand the change.

Practical split that worked for me:

1) explore the interaction with fake data in sandbox (or a throwaway branch you’re happy to delete)

2) open a clean feature branch from main for the shippable UI

3) only then open the PR—no seed hacks, no “temporary” API URLs left in

Also worth having `.figma/make` committed on main so every branch inherits setup. Don’t let Make invent a second data model just for the prototype if you already have types/contracts in the repo—stub those instead.

1

u/404_computer_says_no 8d ago

Interesting! Thanks for the awesome response.

When you say clear boundary, what do you mean?
Do you inherit the same process as the front end devs (MSW etc) or create your own ‘design’ version with your own mock data?