Skip to main content

Tesla is moving away from an SDK and instead planning to allow app mirroring from phones to center consoles

behance model s ui redesign

Since Tesla launched the Model S in 2012, the automaker has been talking about releasing a software development kit (SDK) to create a full third-party app ecosystem for its 17-inch touchscreen, which acts as a center console for the Model S and X, but despite several inquiries from eager app developers, there has been little communication about the project until now.

During a special event for Tesla owners in Hong Kong this week, CEO Elon Musk opened up on the subject and said that the company “thought about it more” and is likely moving away from the SDK, and instead planning to allow mirroring of apps from phones to the center consoles:

“As we have sort of thought about it more, the logic thing to do from an app standpoint is to maybe allow apps on your iPhone or Android to project onto the center display, as opposed to trying to create a new app ecosystem. So that is probably going to be our focus in the future to enable you to project apps from your phone to the center screen.”

There are currently a few apps available for the Model S, but they are web browser-based, which offers its own set of limitations. I would assume most developers were hoping for a full native SDK, but the capacity to mirror apps would be considered a step in the right direction.

At the very least, it will gradually help developers tap into Tesla’s rapidly growing user base:

Model S cummulative 2015

Tesla’s strategy change might be due to worries over the security risks of releasing such an SDK. The Model S has been technically “hacked” before, but it required physical access to the vehicle. The hackers literally had to rip off the dashboard, connect a laptop and send a software command to start the car – basically presenting an alternative to “hot-wiring” an electric vehicle. The real threat is considered to be remote access as some are worried that the SDK could facilitate such a breach.

Apple CarPlay or Android Auto integration, which relies on projecting data from smartphone apps, are believed to be relatively safe options to integrate app ecosystems in cars and plenty of manufacturers have jumped on board, but Tesla has been so far staying away from a direct implementation of these systems.

Make sure to follow Electrek on RSS or your favorite social media to get our latest articles on Tesla Motors and the EV industry:  TwitterFacebook or Google+

Featured image: Tesla UI redesign concept by Bureau Oberhaeuser 

FTC: We use income earning auto affiliate links. More.

You’re reading Electrek— experts who break news about Tesla, electric vehicles, and green energy, day after day. Be sure to check out our homepage for all the latest news, and follow Electrek on Twitter, Facebook, and LinkedIn to stay in the loop. Don’t know where to start? Check out our YouTube channel for the latest reviews.


  1. Brian - 7 years ago

    This decision could be driven by an expectation that, in the future, cars will be shared–an autopilot Uber. If that is part of the product roadmap, then it makes sense to just focus on allowing riders to project their phones.

    But yeah, the security stuff is also probably a big driver.

  2. František Kubiš Jr. - 7 years ago

    it is very sad… Smart phone won’t have access to vehicle parameters. So you can’t make app featuring vehicle charging or getting the state of the doors/windows/steering wheel/and so on… It will be just a smart phone app on bigger screen 🙁


Avatar for Fred Lambert Fred Lambert

Fred is the Editor in Chief and Main Writer at Electrek.

You can send tips on Twitter (DMs open) or via email:

Through, you can check out Fred’s portfolio and get monthly green stock investment ideas.