A charging stop already has a location and an arrival. Supercharger Rally gives those two facts a game state: an unvisited Tesla Supercharger can become a target, a captured stop, and progress toward another objective. The stakes are deliberately recreational. Rally is a checkpoint and route-planning companion, not a charging-network, roadside-assistance, vehicle-control, or Tesla product.

This field note follows the public product loop from choosing a target to seeing what the arrival changed. By the end, you should be able to explain where routes, Achievements, Roadbooks, and Trips fit, along with the account, location, safety, and availability boundaries that matter before use.

A stop becomes a checkpoint when the result is visible

The public product flow starts with an unvisited Supercharger. A driver can choose one nearby or ask Rally to build an ordered, checkpoint-packed route. The product's route screen shows that choice as a sequence rather than a vague reason to wander: the first-party example contains nine checkpoints on one optimized route.

The destination still has to reach the car. Rally's documented flow asks the driver to wake the selected Tesla and request the send while safely parked. A route or checkpoint may be incomplete, delayed, inaccessible, or unavailable, and the vehicle command may fail. Those are source-stated limits, not edge copy to hide after the game starts.

With the relevant iOS location access enabled, Rally can recognize an eligible arrival and add the checkpoint to the driver's roadbook. If location remains off, the driver can still browse Achievements, choose start points and destinations, plan routes, send a selected destination, and import eligible Tesla charging history. Background arrival alerts and automatic captures do not work.

That creates a legible loop: choose, drive, capture, inspect the change, then choose again. BaristaLabs' interpretation is that the arrival matters because the product records a specific state transition. The interface does not have to pretend that charging itself changed. It shows that this stop now belongs to the driver's game history.

Source fact: The public product flow documents choosing a target or route, requesting the send while parked, recognizing an eligible arrival with location access, and recording checkpoint and achievement progress.

BaristaLabs interpretation: A charging stop becomes a useful game checkpoint when the player can see what changed after arrival.

Four objects keep the loop from becoming a list of pins

Routes answer the immediate question: which checkpoints should the drive pursue, and in what order? Rally can build a route around checkpoint hunting or toward a destination. That keeps the next action concrete without claiming that the proposed route is always available, safe, or correct.

Achievements answer a different question: why might this stop be worth the detour? The public Achievement Atlas grouped 2,152 public achievements when reviewed on August 11, 2026. They connect charging stops to roads, natural features, history, engineering, charging feats, geographic collections, and deliberately specific oddities. An Achievement is a condition or discovery attached to progress, not a destination list by another name.

Roadbooks connect related Achievements into a theme that can continue across more than one outing. They give the driver a longer thread to follow after a single capture. The product can therefore offer a next target without treating every stop as interchangeable.

Trips look backward. The public Trips page says a driver chooses the first and last eligible charging session, then Rally rebuilds the intervening drive in order. The driver can add names, notes, stops, and selected photos. Private Trip drafts remain in the app's private iCloud storage, with a local copy for offline use, unless the driver deliberately publishes one. A published Trip has its own preview and terms.

These objects do not need equal screen time. They support different moments in one product story: routes organize the next chase, Achievements explain an unlock, Roadbooks sustain a theme, and Trips preserve a completed drive. That division is the product-design choice. It prevents one overloaded map from having to represent intention, reward, collection, and memory at once.

The account connection has a visible boundary

Supercharger Rally is built for iPhone and iPad and requires a Tesla account. Its setup page says Tesla hosts the sign-in screen, so Rally does not see the Tesla password. Rally then asks the driver to choose the exact vehicle and, when that vehicle requires it, complete Tesla's virtual-key approval. The driver returns to Rally so the app can check the selected vehicle's connection.

That statement should stay narrow. The privacy guide says Rally stores an account identifier and encrypted access tokens to keep the account connected. It may receive vehicle status and command results, and eligible history import includes charging-session and matched-checkpoint data. “Rally never sees your Tesla password” does not mean that no account, vehicle, charging, location, or game data reaches the service.

Location and public sharing are separate choices. The privacy guide says Rally does not build a continuous phone-location history. It also explains that public profiles, leaderboards, and published Trips require their own opt-in actions. The legal Privacy Policy, effective August 9, 2026, controls the full details and should remain the publication reference if any privacy sentence changes.

The safety boundary is equally direct. The Terms say to interact with Rally and set destinations only while safely parked, follow traffic laws and access restrictions, and never enter a restricted or unsafe area for a capture or leaderboard position. The game supplies a target. The driver remains responsible for deciding whether the stop and route are lawful and appropriate.

The product decision comes before the download

The reviewed sources do not establish release, adoption, ratings, usage, route quality, command-success rates, or player outcomes. The Support page says Supercharger Rally is being prepared for TestFlight and App Store review, and the official App Store button will activate when a listing is available. As of August 11, 2026, the public site still says the App Store link is coming soon.

The current decision is therefore whether the checkpoint loop is interesting enough to follow, not whether to trust an unsupported success claim. You can visit Supercharger Rally to inspect the first-party screens and public documentation, or see its BaristaLabs product summary. Supercharger Rally is an independent product of BaristaLabs, LLC. It is not affiliated with, endorsed by, sponsored by, or operated by Tesla.

Sources

First-party sources reviewed on August 11, 2026:

BaristaLabs Products: Supercharger Rally
Supercharger Rally home
Achievement Atlas
Trips
Poker Runs
Vehicle setup
Privacy explained
Privacy Policy — effective and last updated August 9, 2026
Terms of Use — effective and last updated August 9, 2026
Support and availability
Credits