Ive been thinking of that 'classify later' workflow. I think of it kind of like facebooks photo tagging, and it might even be better as web app that you get email reminders for to complete entries.
It would also work nicely for background geolocation services, since if the photograph was taken near a restaurant the service could extrapolate those things.
Anyways, I might make this project opensource and build a nice community around it. Depends on whether or not that model would best support my research goals.
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..)
It would also work nicely for background geolocation services, since if the photograph was taken near a restaurant the service could extrapolate those things.
Anyways, I might make this project opensource and build a nice community around it. Depends on whether or not that model would best support my research goals.