Thats another huge design challenge Ive faced, specifically because it really complicates the data model and UI.

Implicitly, since the app presents a list of possible identified foods, and the user can easily check multiple boxes, thats straightforward, but then having the app pull each of those items AND ask the user to estimate portions for each .... gets a little messy.

So I put that complexity off for v2. That use case in particular would also be best off for a web-interface, I think.

What about dividing the whole plate weight by the foods detected? (in Brazil there are many restaurants where you pay by weight, thats why I'm suggesting..)

Theres a company in the bay area trying this approach actually! They look really interesting: https://getsmartplate.com/

Cant compete with that awesomesauce!