You make a very good point. It bothers me when I see rosy predictions of how much better things will be when we have everything in the cloud. There's still way too many places where you can't get a cell signal for me to be convinced to put all my data in the cloud. Maybe as a backup copy but I'm with you. I prefer to keep my data with me.
I agree entirely in the wireless world. IBM's hardware/software/storage solution is not oriented toward wireless consumers users, but Big Data and analytics tha can be quickly configured run and then disassembled--the rental paradigm.
Cloud computing is great when you are connected - and as a mobile society we can gain access to our information from many locations. However, cell phone users are all too aware of the many places in which they cannot get a signal. For WiFi only devices, the problem is much worse since signals may be absent or require expensive subscriptions. I believe in having local access to all my information (hence my laptop computer rather than a mainframe terminal connection). I accept that I cannot have access to the Internet at all times (cannot access Wikipedia for information that I never knew) - but I expect to have access to all my legacy information all the time.
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.