Hidden Camera Hack in Figma Make

Figma Make prototypes can use the real device camera. No… Figma never mentioned it.

While playing with Make, I discovered that you can access the device camera in your published Make app which means you can build fully functional scanning flows without writing code.

Here’s the full breakdown of how the hack works.

1. What This Hack Actually Unlocks

Because the camera works in published Make apps, you can prototype:

• QR / barcode scanning

• KYC & identity checks

• Ticket scanning

• Payment verification

• Any flow where the user points their device at something

This is the first time designers can simulate real hardware in a no-code prototype.

2. What You Need

This hack only works if:

• You’ve published your Make prototype

• You open the link on a real phone (not desktop)

• Your flow includes a screen where Make expects a “camera view”

The camera will not activate inside Figma Preview which is why most people don’t even know this exists.

3. How the Hack Works (Step-by-Step)

Step 1 — Create your “Scan QR” CTA

Place a button in your UI, like:

Scan QR Code

This is your entry point.

Step 2 — Add a Prompt That Suggests Camera Intent

This is the key part.

Make responds to intent, even if it’s not a documented feature.

Prompt:

When CTA is clicked, open a camera scanning view with corner indicators.

Make will generate a special “camera mode” canvas it’s not visible in the editor, but it exists in the published output.

Step 3 — Add a Second Prompt for Detection

Because Make reads intent, you can chain the behavior:

Prompt:

When the camera detects a QR code inside the corner indicators, navigate to <your page>.

Even though you don’t see a “QR detection” block in Make, the published app will activate the camera and fire the event.

Step 4 — Publish the App

This is where it comes alive.

1. Click Publish

2. Scan the QR code on your phone

3. Open the app through the published link

4. Tap your Scan CTA

Your camera will turn on with your UI frame on top as if this were a native app.

4. Why This Hack Works

Make’s runtime is built on real React Native primitives.

Camera access is already baked into the stack even if the interface doesn’t expose it yet.

When you write prompts that imply a “camera action,” Make maps that intent to its underlying native module.

So yes you’re using a feature that technically exists, just not officially offered.

You found the backdoor.

5. Practical Use Cases for Designers

This is insanely useful for high-fidelity prototyping:

• KYC onboarding: “Scan Emirates ID”

• Fintech: “Scan card for verification”

• Ride-hailing: “Scan QR to start trip”

• Events: “Scan ticket to enter”

• E-commerce: “Scan product to add to cart”

Engineers and PMs will think you built a real app.

6. Why This Hack Matters

Designers can now test flows that were previously impossible:

• You can run real usability tests

• You can validate scanning UX

• You can show live hardware interactions without writing code

• You can simulate KYC and verification flows before engineering starts

This pushes Make into “functional prototype” territory.

Happy Prototyping!

---