I expect reference designs to help getting a system, subsystem or single chip up and running. They might spark my intuition but are not expected to do so.
The 'typical' design idea is less about the application of something given than about solving a problem with deficient means: working around lack of pins, stretching design limits, and so on. The design ideas I am perceiving are far beyond reference designs. AND: these DIs are the things sparking my imagination!
What could help in a limited number of applications (thinking of SMPS and high frequency designs) is what is given in the better reference designs: layout (hints) and tips on how to address "first order" problems.
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. Are the design challenges the same as with embedded systems, but with a little developer- and IT-skills added in? What do engineers need to know? Rick Merritt talks with two experts about the tools and best options for designing IoT devices in 2016. Specifically the guests will discuss sensors, security, and lessons from IoT deployments.