Emulators are fast and cheap but miss real-world conditions like device temperature and uptime. Test updates on virtual devices first, then run the same code on actual hardware to catch problems users will actually hit.
Yeah, of course. I think, you know, there is a time and a place for emulators and simulators. I think it's a good, you know, quick, cheap way of running your tests, but that doesn't give you the real-world outcome. So personally, what I think is a really good technique and a good way of running these tests is like a hybrid model. So your initial sort of pull requests and updates would run against some simulators, like virtual devices. Mm-hmm. Once you're happy that that's passed, you should then run your code on real devices. Because, you know, the users are going to be using real devices at the end of the day. So, and there's only so many parameters you yourself can design, you know, thinking about like the temperature of where the device is, think about, you know, how many times it's been rebooted that day, or has it not been rebooted in, you know, weeks or months even. So having that real-world layer, I think, gives you immense confidence that the, you know, what you're pushing is going to work in the real world, as well as this kind of like AI cloud world.
