As a daily user of this app, it's really great. There's also an adjust serving size feature which updates the ingredients amounts dynamically once you've made the recipe:

After figuring out how to make the coordinates work, it's so satisfying to use a live-updating drag and drop that previews where the dropped content will go.

Is it over-engineered? Probably, but it helped me build a seamless handoff for concurrently editing state where the only direct point of communication between the two pieces of UI is a disk-backed DataStore.

Let's start with the most straightforward approach: we observe the disk, use it to set the slider's current value, and when the user moves the slider, we update what's stored on disk.

Seems great! We have a single source of truth for the state following unidirectional data flow. But...