The concept isn't new - there are already reset/watchdog ic chips often used in such designs. They allow communication with the Application processor to set-up a timer, whilst also providing protection for the SoC by holding the reset until the power is stable. It's know for years so above sounds more like a reminder than 'innovation'..
The last handheld device I worked on had an FPGA. Software was expected to detect the "power" button after 3 seconds to provide the usual graceful shutdown, but for safety we put in logic to shut off power if the user holds down the button for more than 5 seconds. It's hard to imagine phone designers leaving out such a failsafe feature. Especially since Microsoft has conditioned users to expect a "reset button".
I always scroll to the last page to check the writer's byline: ahah, its a Fairchild guy selling chips. Fair enough, but some of his fixit examples are just fixing terribly bad design in the original smartphones, ie the white screen of death; having to remove the battery... seems they never learn.
I hereby declare that my preference is for a separate watchdog device, but I'd use an on-chip device provided it was independent of everything except the power rails. (I am assuming we are not talking about hi-rel devices here by the way.)
What are the engineering and design challenges in creating successful IoT devices? These devices are usually small, resource-constrained electronics designed to sense, collect, send, and/or interpret data. Some of the devices need to be smart enough to act upon data in real time, 24/7. Specifically the guests will discuss sensors, security, and lessons from IoT deployments.