In my opinion, it's pretty clear that Apple's decision to build some computers in the U.S. is aimed at nabbing a little good will. Google got lots of props when it strategically revealed that it's Nexus Q is made in the U.S.
In my opinion, there is a business case to be made for setting up shop close to customers. But it takes a back seat to the economic arguments associated with building stuff in China and other places.
That said, regardless of the reason, we should applaud this small gesture. Those of us who want manufacturing to revive in the U.S. should take any momentum we can get.
Companies don't deal in macroeceonomic arguments. That's governments' job. Companies worry about the bottom line. Whether it makes sense to manufacture close to the customers or not is entirely a question of cost tradeoffs. It might make sense or it might not. For tiny products like cell phones, I have my doubts.
I was surprised to read this in the paper on my way to work this morning. If I remember correctly, Steve Jobs, in a conversation with the US administration about bringing manufacturing back to the US, said something like "Not only no, but hell no."
So I found this surprising. Maybe the change in management?
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.