I'm not saying it won't work out, but I don't think their plan is manufacturing cars. Maybe it's just licensing the self driving tech along with the infotainment system.

Is Apple an entity with knowledge that it accumulates, develops, and applies or are people who work on and hold key positions in projects the ones that bring forth knowledge, develop it and apply it?

Is company's know-how separate from people working on it, and are people the ones who (can) bring it into the company or are people coming to the company and applying company's knowledge? What happens if either lacks - can a company bring in (group of) knowledge and can a company bring in (a group) of talent without (much) knowledge?

Cases can be made for both, I guess. So, there's no straight answer.

The thought of bringing in 95% new-hires to work on a project in which your company has no experience... I mean, why?

If the primary motivation is money, without sufficient passion, good luck competing with Tesla - where they live and breath electric cars.

In the context of my comment, Tesla's answer to "why" was a bit more inspiring than "we need to enter a new market because our existing markets are saturated"

Phones are toys. Cars kill people and are highly regulated.

Mis-using vehicles while operating on the road is illegal.

Cars are far more tightly regulated both for end-users and for manufacturers.

However, people use cars across broad use cases. Some just commute, but some drive in snow, some need to ford small streams in emergencies, some need to install roof racks, and some want car-seats for infants.

I don't see Apple designing for broad use cases, because it isn't in their culture. And that will be a problem, because cars are not toys that you can choose not to use without large consequences.

    > Your reasoning is excellent.