Show native app only elements on browser App renders in dev mode.

[vlbee]

What does this change?

The Follow button and Listen to Article button on articles require a the native bridget service to render, so they do not appear on App rendered articles viewed in a web browser for local development: eg. http://localhost:3030/AppsArticle/...

This defaults the components to show up in localhost dev mode to facilitate development.

Why?

Screenshots

[github-actions]

Hello 👋! When you're ready to run Chromatic, please apply the run_chromatic label to this PR.

You will need to reapply the label each time you want to run Chromatic.

Click here to see the Chromatic project.

[github-actions]

Deploy build 24681 of dotcom:rendering-all to CODE

All deployment options

• Deploy build 24681 of dotcom:rendering-all to CODE
• Deploy parts of build 24681 to CODE by previewing it first
• What's on CODE right now?

---

From guardian/actions-riff-raff.

[arelra]

Thanks for this.

On balance I think we would prefer if components render deterministically with their expected dependencies (e.g. Bridget) as they would in PROD. This makes rendering and testing deterministic without introducing special (perhaps surprising) workarounds for DEV.

That would mean running DCAR locally with a simulator for the full e2e experience.

We do appreciate this is a slower workflow and we have a long term goal of implementing dependency injection in DCAR that would allow a version of Bridget for local testing purposes.

fyi @JamieB-gu