Best practise tips for modelling state machines
XState is amazing, but one thing developers I work with are getting stuck on is that there is too much choice in how to model. There is too much learning and trial and error just in this, and then they get frustrated if they (for example) end up writing a lot of scaffolding in React to get context in a spawned machine that could be in the parent. 2 minute videos of non-dev best practise tips alongside the developer docs would help guide newcomers!
Large scale app with state machines at multiple abstraction levels
App with complex inputs and visualizations
Example: Excel https://twitter.com/jamestharpe/status/1179732994283769858?s=20&t=S0okSRHdWum4Qyhj4Y3WtQ
[React] Define the best approach way from Parent Actor to Child Actor.
Define the best approach way from Parent Actor to Child Actor instead of forward and introducing a new property. Keep Children Components simple and pure so that doesn't must be known outside of context. Refer the official example: https://xstate.js.org/docs/tutorials/reddit.html#spawning-subreddit-actors
NextJS server side props -> React query -> XState sync
Queue management and timeline schedulers
Syncing machine state between browser tabs or app instances
> Is there an example of syncing the machine state between browser tabs? not browser tabs specifically, but I'd like to see how to sync a machine's state on two different instances of an app. https://twitter.com/alirezavlizade/status/1615661232530366464