Earlier quoted context omitted.
>This puts both points b), c) and e) off the table. I don't see where you're coming from on b/c. Motorola makes great hardware - it would be hard to improve that. What Google can do is provide phones with unlocked bootloaders and the standard "Android Experience" UI. Google can make Motorola better precisely because they are a software company, and they can use that core competency to let Motorola focus on what they…
>I don't see where you're coming from on b/c. Motorola makes great hardware - it would be hard to improve that. That's exactly the problem. Google, as a software company, doesn't currently have to worry about a lot of the issues that the hardware side of Motorola does, like supply chain management(both on the production and disposal side), dealing with retail outlets, directly dealing with cellular service providers…
personally, i'm looking forward to the acquisition so we can have Android devices that match up to the iPhone on a hardware level (emphasis on battery life). but the biggest concern i have is how Google is going to deal with the bureaucratic system that they will inherit from Motorola.
i'm currently working in the mobile industry, and a lot of manufacturing companies (Motorola included) indeed have a "very corporate" engineering culture. there are many levels between the devs/test engineers and the customer (whether it be the chip providers, service providers, other manufacturers) and the higher ups within the company. although Google is already a large company, i feel that they make an effort on minimizing the "corporate feel" and that a lot of engineers are attracted to that effort. but with this acquisition, will top-talent engineers get turned off? or will Google be able to minimize/eliminate the inefficiencies between the Google devs and Motorola engineers?
ps: i'm happy to finally be a part of the HN community :)