> The rice cooker doesn't know either, it will take whatever is needed to take. Short of putting an extensive sensor array and ask you for the kind of rice you put in it, there's probably no way to actually predict it.
Why doesn't it know when it's so consistent every time? How does the ninja know? How does this one know when it's closer to 10 minutes? Seems like you should be able to estimate it down to a within a few minutes at start, then refine that estimate if need be. It's helpful to know whether something will take 15, 20 min or 45 to an hour.
Simple rice cookers have only a 100°C temperature sensor (or switch) that turns off the main element once the water is boiled.
My question is what sensor do they use to detect the difference?
I did some Googling but couldn't find any info.
That's enough to manage a temperature curve and predict the last 10~15min of cooking (mine shows a time only 15min before the end), and doesn't require much input from the user.
But on the other hand, if this is a piece of equipment you use regularly, you'll learn pretty quickly how long each thing typically takes, and after that initial learning period, the fuzzy progress indicator is no longer very valuable, and doesn't seem worth investing the engineering and UX time (and resulting higher product cost).
As a software-oriented community, I understand the impulse to throw code at the situation, but this seems like a situation where the cost of doing so doesn't really help very much. And it might actually make things worse, since most users are conditioned to trust/believe the sensors/indicators they see, and a countdown that keeps dynamically changing/jumping/slowing will confuse quite a few people who don't understand why it's a hard problem to solve.
And I think it's worth noting that this is par for the course with most things related to food prep. I'm always looking up cooking times for various things until I memorize the things that I cook often, and this seems like just another case of doing a quick search for a timetable.
How many times do you use it for the first time? Seems like a bit of an edge case to spend engineering time/add extra parts for.
It's not some edge case, it's literally the biggest question after you push start.
Expecting a cooking tool to hold your hand to this degree doesn’t seem reasonable to me.
Or you could just put the rice in extra early. It will get done early. But it will still be hot and perfect when you're ready to eat?
It feels like you have a big misunderstanding of rice cookers.
Because rice isn't consistent.
This is most apparent with certain varieties - a cup of imported Basmati "Royal" brand will take longer and require more water than the same amount of "Three Elephants" Jasmine rice from Thailand.
Even the same varieties produced by different brands/countries will turn out differently in terms of time required. This relates to differences in climate, storage, processing, and other factors.
Depending on environmental conditions (temperature, etc) and amount being cooked, will vary but the results are repeatable quality rice, rather than a fixed cook time and variable quantity rice.
More expensive but better quality rice.
They had a feature (that I believe it's just integrated into every model now) labeled as "neuro fuzzy", decades before the neutral networks boom. I believe it's really just describing hysteresis. So it's doing things based on feedback from whatever sensors they have, but there's no learning from run to run (based on how you actually use the thing).
I also hate its lack of estimated times.
The rice cooker doesn't know either, it will take whatever is needed to take. Short of putting an extensive sensor array and ask you for the kind of rice you put in it, there's probably no way to actually predict it.
On the quick/normal setting, they taste different. My best image would be on black tea: you can use 95C water or near 100C water, one is quicker than the other to fully extract the flavor, but won't result in the same profile (you might actually prefer the quicker one, your choice)
On the UX...welcome to a world where you buy products of different cultures.
If that helps, many people don't actually follow the dosing cup to the letter and adjust the amount of rice and water to their taste, relative the rice we're using at that time after a few tries (at least I do, and so does anyone I talked to), so there is no guideline that would help us.
I'd perhaps compare it to coffee, there are machines doing it all automatically but they taste bland, and the better tools will expect you to know what you're getting into. Rice cookers are as serious business in Japan as espresso machine in Italy, you won't get a high end machine that catters to people who're not familiar with what's going on.