Recipes should be expressed in a higher-level way

[korfuri]

Recipes are defined as such:

{ "name": "Irish Coffee", "api": "irishcoffee", "ingredients": [ {"index": 7, "time": 5000}, {"index": 8, "time": 2000} ] }

This recipe is problematic for several reasons:

• The format doesn't account for possible evolutions of the hardware that will be required to support more advanced recipes (e.g. shake, add ice, strain, etc.)
• Milliseconds are a terrible unit for volume. Peristaltic pumps usually don't guarantee a fixed debit (in ml/s). As such, each hardware deployment needs to be calibrated at setup and on a regular basis, and the pumps' debits must be stored in the barbot for an accurate conversion from volume to time.

From a recipe writer's point of view, recipes are also problematic in that they require two unique identifiers: the name and the API handle. The API should support access-by-name, and the API handle should be removed from the recipe description.

[stumpyfr]

Thanks for your feedback. We are aware of these problem, that is only the first version as a sample for our students of what you can create in one day. We will now make some major evolutions or we hope, students of our school will make them :).