✅ - Amplify Studio & Figma with multiple backends

[uneven flax]

I am working on an Amplify project with a small team. We all have our own amplify environments and corresponding branches in git.

Our integration branch is named dev, it has it's own corresponding amplify environment.

When a UI update is made in Figma I sync it with Amplify Studio in the dev environment. I then run amplify pull locally and commit changes to our dev branch.

Developers working in other branches then pull in changes from dev to work with the new/modified UI components.

This works well until a developer needs to do an amplify push or pull on their backend. When the CLI is generating the new UI components it overwrites index.js effectively removing the new components.

What is the proper workflow for importing Figma changes when working with a team?

Is there a --disable-ui-gen flag to stop this behavior?

I do not want to link the Figma file to all amplify backends since we create and destroy them regularly.

[twin dagger]

hey @uneven flax, to skip the UI component generation, we can use the --no-codegen flag found here: https://github.com/aws-amplify/amplify-cli/blob/dev/packages/amplify-util-uibuilder/src/commands/utils/shouldRenderComponents.ts#L17
unfortunately, Amplify Studio does not support a multi env workflow.

[unborn plume]

✅ - Amplify Studio & Figma with multiple backends