What this is proving is that consumer behaviour is shifting rapidly with us wanting eye catching food with that ow so fuzzy feeling of something being delivered to you without the need to talk to anyone.
Consumers have a higher perceptual need to satisfy their food desires knowing that cooking for themselves might not make the mark.
And with the rise of evergrowing distractions cooking for yourself is a chore now easily avoidable.
Albeit I'll skip trying to rationalise our habits of overindulgence with something that's convenient and satisfying even if it's short-lived...
I've used it for small projects and it's okay. Rq is quite simple and limited in a sense.
I guess what I'd recommend to Mozilla, although fantastic work, is that's it worth trying to compute certain features (data points) upfront to simplify the main model. These calculated features can be used as inputs to the main model possibly reducing the response time.
Then how do you support it? What happens when you need to upgrade or fix a bug?
It's nice to hear that you'll support different needs but be careful as this could cause unnecessary complexities and take you away from developing the core product and improvements. Makes me cringe thinking about supporting different versions of the same product.
I'd suggest stick to the cloud offering and get compliant with gdpr and soc etc
It's the punishment for not getting the answer right! I thought the same initially, to show the explanation after every try but the explanation comes as reward once you get it right. You get unlimited chances to guess the wrong ones so might as well force the learning of the question and reward it with the info.