This would help simulate the situation in the app more accurately on the Composer canvas.

Can it be simpler? I spent almost a week in front of the computer. I still can't understand how I can put the value of the input box when a button is clicked. It will be stored in the cloud data and then not in the label component. Find the information that can display the cloud data end, why not directly put the logical components of all components on the same page, let us change the individual properties if you need the buttons, you can separate the whole process, and several users will Use it, now people have to be simple

The plan is to migrate to 2.0.0 of https://github.com/react-native-community/react-native-permissions Once that's done, we'll bring the ability to ask individual permissions without triggering any other native APIs, as well as rework the permissions asking flow to more closely resemble the spec of react-native-permissions v2+

Event node outputs should define a schema. Now I have to explore the event value object to see what is available for use in further flow function nodes.

Now formulas use `outputs["12afeaafea-3243fa"].codeContent` type syntax, when it should be `outputs.scan_qr_code_1.codeContent` (or `outputs["Scan QR code 1"].codeContent`)

Now there's no validation for many of the values, e.g. any time there's a theme variable that sets a border style, its possible values should be `none`, `solid`, `dotted` or `dashed`.

I should be able to edit a text component directly by double-clicking on it on the canvas.