currentQuantity
can be defined to be a number, and newUser
to have certain object structure.pageVars
namespace in formulas.data
namespace in formulas.appVars
namespace in formulas.params
namespace in formulas.theme
namespace in formulas.translations
namespace in formulas.systemVars.dimensions.window.width
, and systemVars.os
will be different on Android vs. iOS.systemVars
namespace in formulas.sensorVars
namespace in formulas.currentUser.name
app variable, and a Button's text color could be bound to the $colorInformative
theme variable. You can even bind a property value to a different component property value.systemVars.dimensions.viewport.width
, which will cause the input field to initialize with the current viewport width.
Since the bound variable is a system varaible, editing the input field will not change the value of systemVars.dimensions.viewport.width
.data.Order.createdAt
date field into a human-readable format, you don't have to implement any extra logic – every time data.Order.createdAt
gets a new value, the formula is re-evaluated and the binding is updated.pageVars.currentInputValue
via a formula to your input field, changes made by the user will not affect the variable.