Yes, that too, of course.
I have some semi reliable info that says Qualcomm will be Google's next partner, for Android Jello...but that's still unconfirmed.
I think it's a good and safe policy for Google to work with different suppliers every time around. The firm certainly doesn't want to isolate any of its chip/device making partners, and it gives Google quite unique insight into each firm.
I think tablets will probably end up being a lot more specialized than they are now. I actually see big potential for "productive" tablets in areas like healthcare (it makes much more sense for physicians to carry around tablets on the ward...) and also for people who work out in the field and aren't often at a desk. In those cases, cell phones just don't cut the mustard, but a tablet well might. In those cases there would be specific programs and applications on them to make them relevant. But I think you're also correct that for the average consumer, a tablet is not going to replace a laptop any time soon, it's just a nice media consumption device - if you can afford one.
It is good to see the progress in unifying the Android OS for both cellphones and tablets. It will help bring focus to the ARM offerings. Tablets can be useful but I personally never see them threatening laptops. I have never mastered using a soft keyboard for more than a short email. I just don't see using a tablet for programs like Coreldraw, Photoshop, Autocad, Sketchup, Visual Studio etc. I just don't see them being ported over to Windows 8 Metro interface. I don't see the full version of Office being ported to Metro either. I would be better served by an Ultrabook with an Intel processor. It will be interesting to see how this plays out.
I think it is to keep as many vendors involved with Android as possible. If you know that one vendor has a lock then you are much less likely to try to break into the market.
Apple and Motorola.
Microsoft and Intel.
Apple gave up turned to Intel because Motorola (ON) simply couldn't meet their needs.
Microsoft is desperate to break the Intel lock because they are totally missing the big growth area (low power). Arm could change this for Microsoft if Windows 8 doesn't suck. It will be interesting to see if Microsoft still knows how to write lean code that doesn't depend on massive processor power to hide its excesses.
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.