Massachusetts certified the first state-level ride-hailing drivers’ union in U.S. history on Friday, a milestone labor organizers are calling the largest private-sector organizing win since Ford autoworkers unionized in 1941. Nearly 70,000 Uber and Lyft drivers across the state now have collective bargaining rights while remaining classified as independent contractors, a framework made possible by a 2024 ballot measure but one that legal scholars warn could face federal antitrust scrutiny.

Jean Fredo, who has driven for Uber for more than seven years, stood outside the Massachusetts State House on Tuesday and described the stress of working longer hours for shrinking pay as gas and maintenance costs climbed. “I live with stress, always scared to lose my app. This is not a way to live,” he said in French through a translator, holding up a photo of his four children. Drivers hope the union will bring relief on wages, sudden deactivations, and the opacity of app algorithms that determine their earnings.

What the 2024 Ballot Measure Changed

The certification became possible after Massachusetts voters approved a 2024 ballot measure creating a first-in-the-nation framework allowing ride-hailing drivers to unionize and bargain collectively while remaining independent contractors. The model sidesteps federal labor law, which generally excludes independent contractors from collective bargaining protections under the National Labor Relations Act (NLRA, the 1935 statute governing private-sector union rights).

Under the Massachusetts framework, drivers retain the flexibility to set their own schedules and use their own vehicles, but gain the ability to negotiate collectively over pay rates, deactivation policies, and other terms. The ballot measure passed with 53.9% support in November 2024, overcoming opposition from business groups that argued the hybrid model could expose companies to antitrust liability under the Sherman Act, which prohibits agreements among independent businesses that restrain trade.

Victoria Acosta, a mother who drives for both Uber and Lyft, said in Spanish through a translator that she hopes the victory inspires drivers in other states. “Without the support of the drivers, we wouldn’t be here,” she said. Labor organizers are already targeting similar campaigns in California and Illinois, where app-based gig workers face the same classification dilemma.

Why Independent Contractors Cannot Unionize Under Federal Law

Ride-hailing drivers are generally classified as independent contractors rather than employees, a distinction that excludes them from many traditional labor protections. The NLRA covers only employees, not independent contractors, meaning drivers cannot form unions recognized under federal law. Independent contractors are also excluded from minimum wage and overtime protections under the Fair Labor Standards Act (FLSA, the 1938 federal wage law).

The classification turns on control. Employees work under an employer’s direction and control; independent contractors operate their own businesses and set their own terms. Uber and Lyft have long argued that drivers fit the latter category because they choose when and how long to work, use their own vehicles, and pay their own expenses. Courts and regulators have split on the question, with some states and agencies finding drivers are misclassified employees, while others have upheld the contractor designation.

Massachusetts’ ballot measure does not reclassify drivers as employees. Instead, it creates a state-level carve-out allowing independent contractors in the ride-hailing industry to bargain collectively, a structure that exists nowhere else in the U.S. The legal risk is that collective bargaining among independent contractors could be construed as price-fixing or market allocation under federal antitrust law, which treats independent businesses negotiating together as potential cartels.

The Antitrust Challenge Looming Over the Model

Business groups and some legal scholars have warned that the Massachusetts framework could violate the Sherman Act, the 1890 federal antitrust statute that prohibits agreements among competitors that restrain trade. When independent contractors negotiate collectively over prices or terms, they are technically competitors agreeing to set rates, a practice the Federal Trade Commission (FTC, the federal antitrust enforcement agency) and the Department of Justice have historically treated as per se illegal.

The concern is not hypothetical. In 2015, the FTC blocked a proposed rule in Seattle that would have allowed ride-hailing drivers to unionize, arguing that collective bargaining among independent contractors would constitute illegal price-fixing. The Seattle rule was never implemented. Massachusetts’ ballot measure attempts to avoid that outcome by framing the bargaining framework as a state labor regulation rather than a private agreement among competitors, but whether that distinction will survive federal scrutiny remains untested.

Autumn Weintraub, executive director of the App Drivers Union, said drivers across the country regularly communicate with one another about changing conditions in the industry. “Drivers now have an official organization and can speak with one voice about what’s happening in this industry,” she said. “We cannot let billions of dollars leave Massachusetts and go to Silicon Valley. That money feeds people’s families, that money pays the rent.”

How Other States Are Watching

California and Illinois labor organizers are closely tracking the Massachusetts certification. California’s Proposition 22, approved by voters in 2020, classified app-based drivers as independent contractors and provided limited benefits but did not grant collective bargaining rights. Illinois lawmakers introduced a bill in early 2025 that would create a similar framework to Massachusetts, allowing drivers to unionize while remaining contractors. The bill has not yet advanced out of committee.

What Uber and Lyft Said

Uber said in a statement that it would work with the union and regulators while preserving “driver flexibility and hard-won benefits.” Lyft said it was committed to “engaging in good faith” and “helping drivers succeed while keeping rideshare affordable and dependable for everyone who counts on it.” Neither company indicated it would challenge the certification in court, though both have historically opposed efforts to reclassify drivers as employees or impose collective bargaining frameworks.

What Drivers Hope the Union Will Deliver

Drivers who signed union cards cited three primary grievances: declining pay, sudden deactivations, and the opacity of app algorithms that determine earnings. Fredo said when he started driving for Uber he appreciated the flexibility and the ability to make his own schedule while still being present for his family. But over time, he found himself working longer hours while earning less as gas and maintenance costs climbed.

Deactivations are a particular source of anxiety. Drivers can lose access to the apps with little warning, often after a customer complaint or a drop in their rating below a platform-set threshold. The apps do not disclose the specific algorithms that calculate ratings or determine which drivers receive which ride requests, leaving drivers with limited visibility into how their earnings are set.

The union’s first bargaining priorities are expected to include minimum per-mile and per-minute rates, a transparent appeals process for deactivations, and disclosure of the factors that determine ride assignments. Massachusetts regulators are separately considering new ride-hailing rules involving safety standards and driver oversight. Days before the union certification, Uber warned in a blog post that some of the proposals could raise costs and reduce flexibility for drivers, while supporters said the changes are intended to strengthen safety and accountability.

The Autonomous Vehicle Shadow Over the Victory

The organizing effort has unfolded alongside the rapid expansion of autonomous vehicle technology. Waymo, the self-driving subsidiary of Alphabet, has expanded driverless taxi operations in cities including San Francisco, Los Angeles, and Phoenix, heightening anxiety among some ride-hailing drivers about the future of their jobs. Massachusetts still requires a licensed human operator inside autonomous vehicles tested on public roads, but that rule could change as the technology matures.

Weintraub said drivers regularly communicate about the expansion of autonomous vehicles and the threat they pose to driver livelihoods. “Drivers now have an official organization and can speak with one voice about what’s happening in this industry,” she said. The union has not yet announced a formal position on autonomous vehicles, but labor organizers in other states have called for policies that would require human drivers in autonomous taxis or impose fees on driverless operations to fund retraining programs for displaced workers.

Fredo said his dream is to save and send his four children to college. “I’m fighting for a better life for them, just like everyone else is fighting for their families,” he said. “I believe we will get there.”

How the Model Compares to Traditional Union Structures

What Comes Next for the 70,000 Drivers

The union will now begin the bargaining process with Uber and Lyft. Massachusetts law does not set a timeline for reaching a first contract, and neither company has indicated how long negotiations might take. The union has not yet disclosed its full bargaining team or the specific proposals it will bring to the table, though organizers have said minimum pay rates and deactivation appeals will be early priorities.

The certification also sets up a test case for whether the Massachusetts model can survive federal legal challenges. If the FTC or the Department of Justice concludes that the framework violates the Sherman Act, the union could be dissolved or forced to restructure its bargaining approach. No federal agency has yet announced an investigation, but business groups have signaled they may file complaints or lawsuits challenging the ballot measure’s constitutionality.

For now, drivers are celebrating. Fredo said he hopes the union will bring better pay, stronger protections against sudden deactivations, and more stability. “With the union, it will not feel like we’re working for nothing,” he said. “Now the money will not only stay in the billionaire’s pockets. The money will actually come to the workers who work very hard.”

Frequently Asked Questions

Are Uber and Lyft drivers in Massachusetts now employees?

No. The Massachusetts ballot measure allows drivers to unionize and bargain collectively while remaining classified as independent contractors. Drivers still use their own vehicles, pay their own expenses, and set their own schedules.

Can drivers in other states form similar unions?

Not yet. Massachusetts is the only state with a legal framework allowing independent contractors in the ride-hailing industry to unionize. California and Illinois labor organizers are pursuing similar campaigns, but no other state has passed enabling legislation.

What will the union negotiate over?

The union is expected to bargain over minimum pay rates, deactivation policies, algorithm transparency, and other terms that affect driver earnings and job security. The scope of bargaining is defined by the 2024 ballot measure and Massachusetts state law.

Could the union be challenged in court?

Yes. Business groups and legal scholars have warned that collective bargaining among independent contractors could violate federal antitrust law, which prohibits agreements among competitors that restrain trade. No federal agency has yet announced an investigation, but challenges are possible.

How many drivers does the union represent?

The union will ultimately represent nearly 70,000 Uber and Lyft drivers across Massachusetts, according to organizers. The certification was completed on Friday, May 23, 2026.

Will the union affect ride prices?

Uber and Lyft have not said whether they will raise prices in response to the union. The companies have historically argued that higher driver costs could lead to higher fares, but the union has countered that the companies can afford to pay drivers more without raising prices.

What happens if autonomous vehicles replace human drivers?

The union has not yet announced a formal position on autonomous vehicles. Labor organizers in other states have called for policies that would require human drivers in autonomous taxis or impose fees on driverless operations to fund retraining programs for displaced workers.

The Trump Accounts mobile app goes live Thursday, giving millions of American families instant access to manage their children’s federally seeded investment accounts. Built by Bank of New York Mellon and Robinhood Markets Inc., the app arrives on Apple and Google app stores as the delivery mechanism for the administration’s 530A program, which deposits $1,000 into accounts for every child born between January 1, 2025, and December 31, 2028.

Families who enrolled early can activate accounts immediately. Federal contributions hit on July 4, after the official rollout. Account holders get financial literacy materials baked into the interface.

What the 530A Program Actually Delivers

The 530A accounts hand eligible U.S. citizens with Social Security numbers a $1,000 federal stake. Parents, relatives, employers, and charities can add up to $5,000 annually on top of that. The default investment at launch is an S&P 500 exchange-traded fund.

Treasury Department projections estimate the initial $1,000 alone could grow to roughly $5,800 by age 18 and nearly $200,000 by age 55 without additional contributions, assuming historical market returns. President Trump framed the program in January as a birthright:

More than 1.1 million Android apps were quietly removed from Google Play in a single quarter of 2024, according to Pixalate’s quarterly delisting report. Almost none of the users who had those apps installed received any warning.

A teardown of Google Play Store v51.4.19, published by Android Authority on May 26, surfaced three notification strings that will finally tell Android users when an installed app has been pulled from the Play Store. The feature isn’t live yet, and Google hasn’t set a date, but the engineering work is in the build.

The Strings Hidden in Play Store v51.4.19

Aamir Siddiqui, the APK teardown specialist who flagged the find, pulled apart the latest build and surfaced three notification strings sitting dormant in the code. They are short, formal, and tuned for three different removal scenarios.

• %1$s was removed from Google Play and will no longer receive updates
• %1$s and %2$s were removed from Google Play and will no longer receive updates
• %1$s and %2$d other apps were removed from Google Play and will no longer receive updates

The first string handles a single removal. The second covers two apps in one notification. The third batches multiple removals into a single alert, the format Google would use when a developer’s whole catalogue gets pulled at once or when a publisher voluntarily exits the store on the same day.

Teardown findings carry a familiar caveat. Strings discovered inside an APK can ship, get scrapped, or sit in the build for months before activation. The version number tells you the work is real engineering, not a mockup, but it doesn’t promise a public release.

The phrasing rewards a slow read. “Will no longer receive updates” is the operational meaning. The app on your phone keeps working until something else breaks it, but the patch pipeline is closed. For anything with a server backend, the notification doubles as a quiet countdown: when the developer stops paying for cloud bills, the install on your device becomes a husk.

Why Play Has Stayed Quiet on Routine Removals

The current Play Store only contacts users about an installed app under one trigger: when it’s flagged as a security risk. The work runs through Google Play Protect’s on-device scanner (GPP, the malware service bundled with Play Services on every Android phone). When GPP spots a known bad actor, it pushes a notification with a one-tap uninstall.

Everything outside that trigger has been silent. A developer who lets the Play listing lapse, an indie studio that retires an old title, an app pulled for a minor policy issue: none of those send any signal to the people still using the app. The icon sits on the home screen. The shortcut still launches. The version is frozen at whatever the last update shipped. Most users find out by accident, when they try to reinstall on a new phone and the search returns nothing, or when a friend asks where to download it and the link is dead.

The new strings change that default. They read like a courtesy heads-up, not a security siren. The operational implication is clear: no patches are coming, and the install on your phone is the last version you will ever get. That single nudge, repeated across hundreds of millions of devices, becomes the first time Play has acknowledged routine delistings as something worth telling users about at all.

A Delisting Graveyard in the Millions

The reason this matters is the sheer scale of what Google has been clearing out in silence. The ad-fraud research firm Pixalate has been tracking quarterly Play Store delisting since 2022, and the numbers climbed sharply through 2024.

The Quarterly Numbers

Each row above counts apps that disappeared from Google Play during the period, either pulled by Google or by the developer. The Q2 figure represented 34% of all apps live on the store at the start of the quarter, a wave-scale clearout that almost no end user heard about in real time.

The Abandoned-App Share

Pixalate defines “abandoned” as an app that has gone more than two years without an update. In Q2 2024, 74% of delistings were abandoned apps, up from 25% in the same quarter a year earlier. The composition matters. A delisting wave dominated by abandoned apps tells you Google is clearing dead inventory at scale, not policing live ones.

What the Trend Says

The volume also explains the shape of the new notification system. With abandoned-app removals running into the hundreds of thousands per quarter, the typical user almost certainly has at least one ghost app on their phone right now. Building a one-line alert and shipping it through the standard Play notification channel is a low-cost way to surface that fact without flooding users with security-grade red banners.

It also reframes the question of urgency. If the share of abandoned delistings keeps climbing the way 2024 suggests, this alert is closer to a triage signal than a marginal nicety.

Three Reasons an App Vanishes

The teardown didn’t show separate strings for different removal causes; the same wording fires regardless. But the cause matters for what a user should do next, and recorded reasons for Play Store removals usually map to one of three buckets.

• Developer self-delisting. The owner pulled the app voluntarily, often because a service shut down, a small studio went under, or a publisher consolidated titles. The install on your phone keeps working as long as the backend is alive.
• Google policy action. Play removed the app for violating Developer Program Policies, covering data-handling failures, deceptive behavior, or repeated minor breaches. These removals tend to coincide with media coverage when the offender is large.
• Target API enforcement. Under Google’s target API level policy, apps that don’t compile against a recent Android SDK lose discoverability for new users on newer Android versions.

That third bucket is the cleanest match for the abandoned-app surge. Each year the floor moves one API level higher. New apps and updates submitted after August 31, 2025 must target Android 15 (API level 35).

Apps that miss the deadline don’t get a takedown email; they just stop appearing in search results for new devices. From the user side, the experience looks identical to a hard removal.

The new notification doesn’t distinguish among the three. A reader who sees the alert has to do their own follow-up to figure out which bucket their app fell into.

What This Changes for Developers and Power Users

If the strings ship, the change will ripple outward in directions Google hasn’t framed publicly.

For developers, the optics shift. A silent delisting used to mean only the most engaged users noticed. With the new alert, every active user gets a system-level message that this developer’s app is dead. Studios will start treating an unannounced delisting the way they treat a server shutdown, with a blog post, an outreach email, and a planned communication window.

Smaller developers face a stickier problem. Many casual or hobby apps drift into abandonment because the developer changed jobs, lost interest, or moved off Android. Those builds will start lighting up notification panels on devices that haven’t opened the app in years, surfacing the long tail of solo-developer churn that has historically stayed invisible.

Power users gain a useful audit signal. An Android phone older than two years probably has a handful of ghost apps quietly occupying storage, holding permissions they shouldn’t still have, or just clogging the app drawer. The alerts give those users a recurring prompt to clean up.

The shift also tracks a wider pattern of Google closing communication gaps with users. The Chromecast support-table episode in May showed how absent messaging about device lifecycles can turn into a public scare overnight. A Play Store notification for routine app removals is a far smaller commitment, but it lands in the same direction.

Google has set no public timeline for the rollout. The strings are present in the build but inert. A future server-side flag could flip them on for everyone, for a regional rollout, or never.

Frequently Asked Questions

When Will Google Roll Out the App Removal Notifications?

Google has not announced a release date. The notification strings exist inside the latest Play Store build but are not yet active for users. APK teardowns surface in-progress code, and Google sometimes ships these features within weeks, sometimes after months, and occasionally not at all.

Can I Check My Android Phone for Apps Already Removed from the Play Store?

There is no built-in tool yet. The simplest manual check is to open the Play Store, search for each installed app by name, and confirm a current store listing appears. Third-party utilities such as AppNotifier on the Play Store can also flag installed apps that no longer have a public listing.

Will a Removed App Still Work on My Phone?

Usually yes, at least for a while. A removal from the Play Store stops future updates but does not uninstall the app from your device. Apps that rely on a live server backend will stop working once the developer shuts the backend down. Fully offline apps can keep running for years.

What Is Google Play Protect and How Does It Differ from the New Alert?

Google Play Protect is the on-device malware scanner bundled with Play Services. It already notifies users when an installed app is flagged as a security threat and offers a one-tap uninstall. The new removal alert is separate: it covers routine, non-security removals that Play Protect has always ignored.

Why Does Google Remove Apps from the Play Store?

The three most common reasons are developer self-delisting, policy violation takedowns by Google, and target API level enforcement that quietly removes apps from search results for newer Android devices. The bulk of the volume comes from abandoned apps, those without an update in two-plus years.