Technology

Also Pauses TM-B Launch Edition Deliveries to Fix Software Faults

Martin HollowayPublished 3m ago4 min readBased on 1 source
Reading level
Also Pauses TM-B Launch Edition Deliveries to Fix Software Faults
Photo by Himiway Bikes on Unsplash

Also has paused customer deliveries of its Launch Edition TM-B e-bikes after identifying software-based issues, including charging behavior. The company told customers about the pause in an email sent this week, according to The Verge.

Also is a mobility startup that spun out of Rivian in 2025. Before the pause, it had almost finished shipping the Launch Edition bikes and had planned to move on to the Performance Edition. That transition is now on hold for Launch Edition deliveries, and the company is working on a firmware update, the low-level software that controls the bike's hardware, to address the TM-B software issues.

The delivery timeline is also moving. Senior PR manager Michele Mehl said the TM-B timeline will be delayed beyond what was previously communicated to customers waiting for their bikes. Also plans to send another update on the delivery delay on November 24.

The product is built around a few design choices that matter for the current problem. The TM-B battery charges over USB-C and comes in 538Wh or 808Wh packs, with up to 100 miles of range. The bike uses pedal-by-wire, meaning there is no mechanical connection between the pedals and the movement of the bike. Pedal input is read electronically, and the drive response is set by software and firmware.

That architecture explains why the company describes the problems in software terms. On a conventional bicycle, a chain and crank link the rider's leg force directly to the drive wheel, with assist electronics sitting on top of that link. With pedal-by-wire, the control software sits between rider input and propulsion, so charging logic, battery communication and drive response all share one firmware stack. Validating that stack across every charging and riding state is a bigger job than a typical software patch, and the schedule slip reflects that.

The broader context here will be familiar to anyone who follows automotive and consumer electronics. Software-defined hardware moves the cost of a defect from the factory floor into the release pipeline. A fault that a mechanical part would reveal during assembly can surface after the product is in customers' hands, and the fix arrives as an over-the-air or service-level update instead of a replacement part. That approach corrects errors efficiently when the update path is well tested. It also makes delivery dates harder to predict once a company has started shipping and then needs to stop.

For customers, the immediate effect is a longer wait and a second round of revised timing. The November 24 update is the next concrete point for buyers of a Launch Edition unit, and it will show whether the firmware work is on the schedule the company now expects. Owners and pre-order holders will want to read the details before deciding how to plan.

In my view, the more useful measure for a new mobility company is how it handles a pause like this one. Stopping shipments after nearly completing the Launch Edition run, and telling customers in writing that the timeline is moving, is a visible choice. A firm update date followed by a tested firmware release would show the pause was a controlled correction rather than an open-ended problem. The same architecture that makes the TM-B responsive and easy to tune is what makes its fixes depend on software, and that dependency is the central thing to watch as the company returns to shipping.