This means that the native module is only responsible for its internal state and shared state is kept in React Native. At startup, we pass in whatever is necessary for the module to begin its work, and any shared state is managed in React Native, and updated via the native module (updates from the native module are sent via EventEmitter). Q: How do you synchronize native (KMM) and React Native stateĪ: We try to treat React Native state as the “Source of Truth”. Wiring this up is work, no getting around that. We are adding React Native views in piecemeal, and so navigation is being handled by the existing navigation controllers. Q: Is Shopify Brownfield app? If it is, how are you handling navigation with React Native and Native!!Ī: Shop and POS are both React Native from the ground up, but we do have a Brownfield app in the works. Q: Do you write automated tests using protractor/cypress or jest?Ī: Jest is our go-to library for writing and running unit and integration tests. We utilize padding to create spacing within a component and margins to create spacing between components.Ī: No but a few native android developers coming from the IntelliJ suite of editors have set up their IDE to allow them to code in React and Kotlin with code resolutions using one IDE We use fixed sizes mostly for icons and imagery. This results in your UI being more fluid and adaptable to various devices. and where to use margin or paddings?Ī: Try to keep most things flexible unless absolutely necessary. Q: Do you have any guide on what needs to be flexible and what fixed size. That being said, running into bugs that are internal to React Native isn’t a scenario that we have to handle often, and if it ever happens, we rely on the technical expertise of our teams to understand it and communicate, or fix it through the existing channels.

Pretty often issues on GitHub for some of these 'rare' bugs might stall with no solution, so working on a PR for a fix isn't always a choice (after, of course, submitting a well documented issue).Ī: We rely on various debugging and observability tools to detect crashes and bug patterns.

Q: How do you usually handle running into crashes or weird bugs that are internal to React Native? In my experience some of these can be pretty mysterious without good knowledge of React Native internals. Q: What best practices can we follow when we’re building an app, like for accessibility, theming, typography, and so on?Ī: Our Restyle and Polaris documentation cover a lot of this and is worth reading through to reference, or to influence your own decisions on best practices.

Intellij reactjs