Now you might be implying that abruptly powering off Windows would corrupt the file system, but that kind of wrong thinking belongs in another decade. Windows has used self-repairing journaled file systems for 15 years. Journaled file systems for Linux entered common use in the same year, and you don't think twice about what happens to the file system on your Linux box or Android phone when it loses power.
Well, yes, I do. Every day. For a living.
File system journals (and fsck) help maintain file system integrity, not file integrity nor medium integrity. It's only the middle layer.
If a program has only written half the data to the OS drivers by the time power goes, and those writes are replayed from the journal upon boot, you have a working file system but a corrupt file. I much prefer to be able to signal the apps to complete their output and shut down gracefully.
Likewise, cutting the power during a physical write can cause all sorts of problems, especially on media where the controller lies about whether a write is finished in order to improve write speeds. That includes most consumer hard drives and removable media. The OS removes the write from the journal as committed, while in reality it's still being handled by the hardware. Unless you have a hardware disk controller with battery backup, and turn write caching off on the physical media, this is a very real cause of corruption for power outages, and one a journal can do nothing about.
You mention Android phones. With microSD cards, where there generally is no way to disable caching, the problem is so bad that most phones make it incredibly hard to not do a controlled shutdown. But find that hidden reset switch in your phone, and hit it a few times during operation, and you will likely have corruptions, despite journaled file systems.
Incidentally, the use of non-enterprise journaled file systems is an exploit vector for intruders. If they can find a way to reset the system, and the journal replay helpfully makes valid files out of half-written temporary files, there can be a wealth of information there that shouldn't have been accessible. Good enterprise file systems like JFS and XFS will err on the side of caution and zero files that were read locked and partially written (causing a lot of complaints from those who don't understand why), while more commonly used file systems err on the side of retaining data over security.