Connect with us

News

Tesla launches official API for app store, third-party services

Credit: Tesla China

Published

on

Tesla has launched an official Application Programming Interface (API) for its vehicles, indicating that the company could be looking at debuting its own app store soon.

Without sharing all the system details, Tesla has launched an initial tier of its own API that’s expected to evolve into next year and will eventually cost money, according to a report from Not a Tesla App earlier this week. The new API tier is called the “Discovery Tier,” and while it’s currently free, that’s expected to change moving into 2024 — though Tesla has yet to detail price points or plans for additional tiers.

Eventually, Tesla is likely to debut its own App Store, generating money from developers who want to develop and host their own services and apps on the automaker’s in-car platform. The current Tesla API is primarily geared toward fleet management, as seen in the Not a Tesla App image below or on the company’s website here.

Credit: Tesla (via Not a Tesla App)

An API works by bridging the gap between two software applications, effectively letting third parties build apps and services that work with a given software platform, such as Tesla’s in-car software. The launch of the API means that Tesla will be shifting away from the use of its REST API, which is currently in use, and the company’s official API will likely be in full use with multiple tiers and price levels as soon as next year.

While Tesla can offer official support for apps hosted on its API, and the move should result in improved integration and better user control over permissions, the shift will also increase costs and could place limits on specific functions. As Not a Tesla App points out, it may be easy to adjust to for larger third-party services, such as Uber, though smaller open-source software, such as TeslaMate, may have a difficult time transitioning to the API.

Advertisement

In the past, engineers have managed to reverse-engineer Tesla’s API to create third-party apps for tracking certain vehicle details and pushing notifications, and some have even used this method to develop fleet management software. Tesla’s “Discover Tier” is set to allow one data request per car every five minutes, though some services require far more frequent data requests for use.

Tesla Apps | Dutch Developer Leverages Real-time Electricity Rates for Charging

Users can navigate to Tesla’s API sign-up on its website here to access Tesla’s API endpoints. Through doing so, Tesla says that an application can request permission to view account and vehicle information from owners and issue remote commands such as unlocking and locking doors, accessing the horn and other similar functionality.

The news reminds us of when Tesla CEO Elon Musk took over Twitter (now X), and how he went on on to revamp the social media platform’s API. Previously free, X created tiered charge levels for its API, some of which are thousands of dollars each month. Some developers simply ended their services upon the shift, while others charged their users more for the software.

Advertisement

After the X API implementation, Musk also threatened to sue Microsoft for allegedly using the company’s data after the company had complained about the change.

Twitter bans third-party clients in developer term update

What are your thoughts? Let me know at zach@teslarati.com, find me on X at @zacharyvisconti, or send your tips to us at tips@teslarati.com.

Advertisement

Zach is a renewable energy reporter who has been covering electric vehicles since 2020. He grew up in Fremont, California, and he currently lives in Colorado. His work has appeared in the Chicago Tribune, KRON4 San Francisco, FOX31 Denver, InsideEVs, CleanTechnica, and many other publications. When he isn't covering Tesla or other EV companies, you can find him writing and performing music, drinking a good cup of coffee, or hanging out with his cats, Banks and Freddie. Reach out at zach@teslarati.com, find him on X at @zacharyvisconti, or send us tips at tips@teslarati.com.

Advertisement
Comments

News

Tesla’s Navigation Nightmare: Why the easiest part of FSD might be the hardest

Published

on

Credit: TESLARATI

Turn-by-turn navigation is not new technology.

For over two decades, drivers have relied on Garmin, TomTom, and later smartphone apps like Google Maps and Waze to receive precise, reliable directions. These systems have guided millions safely through unfamiliar cities, highways, and backroads with remarkable effectiveness. They handle real-time traffic, construction detours, and complex intersections with minimal fuss.

Yet Tesla, the company that promised revolutionary Full Self-Driving (FSD), continues to struggle with this foundational capability. As FSD (Supervised) v14.3.4 has started rolling out to cars this week, navigation remains its glaring Achilles’ heel, undermining the entire autonomous vision.

Tesla Summon got insanely good in FSD v14.3.2 — Navigation? Not so much

Advertisement

Tesla’s FSD excels in many driving behaviors—smooth acceleration, confident lane changes in ideal conditions, and responsive handling of visible obstacles. However, when it comes to following a route accurately, the system falters repeatedly.

Owners report wrong turns, missed exits, inefficient routing through local roads instead of highways, phantom speed limit errors, and even directing vehicles to building rear entrances. Interventions for navigation issues often outnumber those for core driving maneuvers. Tesla has begun surveying owners specifically about these errors, acknowledging the problem after years of complaints.

Navigation is perhaps my biggest complaint when it comes to FSD, because sometimes, we do know better. Some of us have been living in our areas for our entire lives, but even those who have not have years or even decades of experience driving on local roads. We might know a little better about routing.

But the navigation mistakes are more than just FSD potentially taking a slightly different route that may or may not save you a few minutes. Sometimes, they’re genuinely mind-boggling.

Advertisement

This isn’t just annoying; it cascades into broader failures. A flawed route plan confuses the AI’s decision-making, leading to hesitant behavior, unnecessary disengagements, or dangerous maneuvers like attempting impossible U-turns or ignoring clear ramps. In a system meant to operate with minimal supervision, unreliable navigation erodes trust.

More often than not, false or plain incorrect navigation is what causes me to interrupt FSD operation. Unfortunately, I believe the latest FSD version is the worst example of it, and it leads me to believe that Tesla might be making some changes; they’ve just made them in the wrong direction.

It makes you wonder: Why is a company that has done so much with the progress of FSD and autonomy struggling so much with navigation, something that is not new and has been around a long time?

Multiple Data Sources

First, Tesla’s navigation relies on a fragile patchwork of multiple data sources—Google Maps, TomTom, OpenStreetMap, Valhalla, and its own fleet-derived data—stitched together rather than a single authoritative map. When these conflict on lane geometry, road status, or turn details, the system hesitates or chooses incorrectly.

Advertisement

Traditional GPS providers maintain centralized, regularly validated databases with professional curation and rapid updates. Tesla’s hybrid approach, while innovative in crowdsourcing, introduces inconsistencies that a purely vision-based or end-to-end AI approach may not easily reconcile in real time.

Persistent Learning

FSD seems to struggle with persistent learning from driver interventions.

Unlike consumer apps that quickly adapt to repeated corrections or user preferences (e.g., avoiding certain routes or remembering habitual detours), Tesla’s FSD often fails to internalize fixes on the same trip or across similar scenarios. Owners note making the same manual override multiple times without the routing engine updating its behavior meaningfully.

This stems from the neural architecture prioritizing real-time perception and control over long-term route memory and personalization, making navigation feel rigid and “opinionated” compared to the adaptive logic in Waze or Google Maps.

Advertisement

I noticed that when I asked Grok to try and get me home a certain way (a way that FSD routinely took in the past because it was the most efficient), it had to place a waypoint between my location at the time and my house. When I went to edit the waypoint out, as Grok had placed it for a way to get FSD to get off the highway at the right exit, it was stumped again, rerouted, and took a longer way home.

Reasoning, Scaling, and Intuition

Third, scaling navigation for unsupervised or robotaxi ambitions requires not just accuracy but adaptability and user-like reasoning. Current FSD often defaults to single routes that ignore driver preferences or real-world nuances like time-of-day traffic patterns. It fails to match the intuitive, context-aware planning that traditional systems have refined over the years.

Resolving navigation is critical for several reasons. Practically, it is the backbone of any autonomous journey: without trustworthy routing, the car cannot reliably reach destinations, rendering FSD useless for robotaxis or hands-free commutes. Safety depends on it—mismatched plans create hesitation in merges or intersections, increasing accident risk.

Economically, Tesla’s valuation and future hinge on FSD delivering unsupervised driving; persistent navigation flaws delay regulatory approval and erode consumer confidence. For owners who paid premiums for FSD, these issues represent unfulfilled promises. While it is unlikely Tesla will lose too many customers due to bad navigation, some will be frustrated with the constant need for human input.

Advertisement

Tesla has achieved miracles in electric vehicles and battery tech. Mastering turn-by-turn—technology Garmin nailed in the early 2000s—should not be this hard. By investing in tighter data integration, faster learning loops from interventions, and more intuitive routing algorithms, Tesla could close this gap.

Until then, FSD’s navigation struggles highlight a humbling truth: even the most ambitious innovator must sometimes master the basics before conquering the future.

Continue Reading

Cybertruck

Tesla Cybertruck driver gets pickup seized for ‘legitimate concerns’ in UK

Published

on

A Tesla Cybertruck driver in the United Kingdom had their all-electric pickup seized by local police in the Greater Manchester area after the department cited “legitimate concerns.”

Last Thursday, police saw the pickup on the roads and decided to pull the driver over. Greater Manchester Police said:

“Whilst this may seem trivial to some, legitimate concerns exist around the safety of other road users or pedestrians if they were involved in a collision with the Cybertruck.”

The Cybertruck in question was, according to the BBC, registered and insured abroad and was confiscated. The driver, who is a UK resident, was reported.

The Greater Manchester Police Department then added:

Advertisement

“The Tesla Cybertruck is not road-legal in the UK and does not hold a certificate of conformity.”

The Cybertruck cannot be legally driven in the UK because it has no UK Type Approval for operation in the country. This is due to some safety concerns, which are related to its angular shape and design. The stainless steel exoskeleton has sharp edges and projections that violate UK/EU rules on pedestrian protection.

Tesla has considered creating what it referred to as an “international version” that would be approved for operation in Europe. However, there has been no real movement on that front by the company, as it has been focused on the Robotaxi rollout primarily.

Advertisement
Continue Reading

News

Apple is developing the missing link for Tesla to get CarPlay: report

Published

on

Credit: Michał Gapiński/YouTube

A new report claims that Apple is in the process of developing what would be the missing link for Tesla to get CarPlay.

Apple and Tesla have been reportedly working together for some time to give Tesla owners the opportunity to utilize CarPlay within their vehicles. While many owners are more than happy with Tesla’s in-house UI, which is seamless, effective, and smooth, some still want CarPlay, which does have its advantages.

A report from 9to5Mac now states that a new CarPlay technology that was highlighted during the Worldwide Developers Conference (WWDC) would potentially be the bridge between Tesla and Apple. With the addition of a feature known as “Route Sharing,” which gives a navigation app the ability to share routing data with the vehicle, Tesla would be able to launch CarPlay in its vehicles, the report states.

CarPlay has not been a priority for Tesla because it has done extremely well with its in-house UI, but some drivers are just used to it. Additionally, it could improve Tesla’s subpar Navigation or offer improved app capabilities, especially with iMessage.

Advertisement

Route Sharing is an intended addition to CarPlay’s iteration in iOS 26.4, which was released in March:

The addition of CarPlay would undoubtedly be welcome, but at the same time, it seems like Tesla realizes it is not of the utmost priority. There are so many things that Tesla is working on currently within its own vehicles, especially attempting to solve self-driving.

Back in February, Bloomberg had reported that Tesla was still working on bringing CarPlay to its vehicles, but it had not due to app compatibility issues and incredibly low adoption rates of iOS 26.

Advertisement

This bottleneck could buy Tesla the proper amount of time to develop CarPlay for its vehicles. It would be a welcome addition, and could be brought on with either the Summer or Fall 2026 Software Updates.

Continue Reading