I'm a Salesforce consultant. Every project I've worked on started the same way: a Figma or grey-box wireframe that the client signs off, then a build that surprises them, because a picture of a Lightning page is not a Lightning page. Hover cards, path chevrons, related lists, the way a quick action opens: none of it is in the mock-up, and the review meeting turns into "is this what Salesforce looks like?" instead of "is this the requirement?".
What I've been doing instead is building the page itself in the real Lightning Design System from the user story, in both the SLDS 1 and SLDS 2 looks, then clicking through it with the client and reading the acceptance criteria back off the page. It has changed our review meetings, but I'd like to know what others in this group use:
Do you prototype in the SLDS Figma kit, or straight in App Builder in a sandbox?
How do you show interaction (quick actions, screen flows, popups) without building it for real?
How do you handle the SLDS 2 transition when the client's org still shows the classic look?
Full disclosure: I built the tool I use for this (
sfproto.com, free to try, nothing connects to an org). That's not the point of the question, but I'd rather say so than not.Not a Figma expert but they did showcase the look, feel and functions, not the actual integration behaviour, map layer data, features, workflows etc. The actual functionality was left to the build. I think that is one of the reasons why designs sometimes had last minute rework because by the time developers started building, something changed.
