The Old Phone
I began by wondering whether an old phone could be given a second life.
It was a Samsung Galaxy S20 FE: no longer my primary device, but still a remarkably capable object. Its screen worked. Its battery held charge. Its cameras, processor and radio had not forgotten their purpose. There was no practical reason it could not make calls, carry maps, play music, hold books, help me write, and accompany me through another few years of ordinary life.
The plan seemed simple enough. Factory-reset it. Leave the Google account behind. Install F-Droid, the independent catalogue of free and open-source Android software. Perhaps, if the exact model allowed it, replace Samsung’s operating system with LineageOS and discover how much of a smartphone could still function beyond Google’s embrace.
Then the small project opened into a much larger question.
If I bought the phone, why did reclaiming it require research into bootloaders, security fuses, proprietary services, application verification and the conditions under which software might be installed? Why did ownership feel less like possession than a licence to use an object within somebody else’s continuing permission?
The phone had not become obsolete. Its obedience had become complicated.
The Everyman’s Promised World
For those of us who remember the early public internet, Google did not first arrive as a behemoth. It arrived as relief.
The web was expanding faster than anyone could organise it. Search engines were cluttered, unreliable and easily gamed. Google offered a white page, an empty box and the quietly astonishing promise that the world’s information might be made useful to anyone who could type a question. It seemed less like an institution than a public utility that had somehow appeared before the public knew to ask for it.
Its gifts accumulated.
Gmail made abundant storage feel ordinary. Maps turned an unfamiliar city into navigable ground. Docs allowed people to write together without buying office software. YouTube became a library, stage, classroom, archive and unruly town square. Android offered manufacturers and users an alternative to Apple’s tightly controlled mobile world.
This was the Everyman’s promised world: knowledge without the old gatekeepers, tools without the old price of entry, publication without permission, direction without an atlas, communication without distance.
Google did not seem to own the road.
It seemed to be laying roads where none had existed.
And because so much of it was free at the point of use, we confused accessibility with public ownership.
We mistook a generous entrance for a commons.
Free Became Familiar
There was no single morning on which the promise turned into enclosure.
That is not how dependency usually forms.
A service becomes useful. Usefulness becomes familiarity. Familiarity becomes habit. Habit becomes expectation. Expectation becomes infrastructure. By the time the terms change, leaving no longer means choosing a different product; it means disturbing the architecture of everyday life.
Schools organise classrooms through Google. Small organisations keep records in Drive. Writers discover that their work exists inside Docs, their correspondence inside Gmail, their photographs inside Photos, their directions inside Maps, their audience behind Search, and their website’s survival inside an advertising market Google helped to shape.
The problem is not that Google charges money.
New work costs money. Engineers must be paid; data centres do not run upon benevolence. A paywall around a new luxury is commerce.
But a toll gradually placed upon a route people were encouraged to experience as ordinary infrastructure begins to resemble governance.
Google did not merely sell services. It helped define what ordinary digital life would look like, then acquired increasing authority to decide which parts of that life remained freely available, which required payment, and which could function only through its accounts, standards and approvals.
Convenience did not take our freedom away. It made us forget to ask where our freedom had gone.
It Did Not Invent the World It Came to Govern
Google’s growth is often remembered as though one astonishingly inventive company simply kept producing the future. Search led naturally to advertising; advertising to video; video to phones, maps, documents, navigation, domestic devices, health data and artificial intelligence.
But that is not quite how the future was made.
Android was once a small independent company. YouTube belonged to its founders. Keyhole became the foundation of Google Earth. Where 2 Technologies built core technology that became Google Maps. Urchin became Google Analytics. Writely evolved into Google Docs. DoubleClick brought advertising infrastructure that would prove central to Google’s position in digital advertising.
Later came Waze, Nest, DeepMind and Fitbit: established companies, technologies and communities gathered into an expanding corporate ecology.
These were not merely products waiting to become Google features. They were independent projects, people, technologies and possible futures.
Google did not simply build an ecosystem.
It purchased streams of independent invention and redirected them into one river.
Some of those acquisitions prospered spectacularly. YouTube became larger than its founders could reasonably have built alone. Android reached billions of people. Google Earth placed the planet beneath the hand of an ordinary computer user.
To pretend that acquisition always meant destruction would be both easy and untrue.
But survival is not the only measure of independence.
A flourishing subsidiary can still represent a vanished competitor. A startup may retain its name while losing the possibility of becoming a separate centre of power. Something need not be destroyed to cease being an alternative.
Others disappear altogether, their people, technology or insight folded into products whose origins are eventually forgotten.
What appeared to users as seamless innovation was also consolidation: many beginnings becoming one infrastructure; many centres of possibility becoming features inside a single company’s future.
The behemoth’s most remarkable appetite was not that it destroyed everything it swallowed.
It was that it could swallow something, enlarge it, rename the landscape around it, and make us forget that it had once stood outside the behemoth at all.
When a Transaction Becomes an Architecture
DoubleClick offers perhaps the clearest warning against viewing each acquisition in isolation.
Google agreed to buy the advertising technology company for $3.1 billion. In 2007, the US Federal Trade Commission declined to block the deal, concluding that the proposed acquisition was unlikely substantially to lessen competition.
Examined as a transaction, the purchase passed through the regulatory gate.
Eighteen years later, a US federal court found that Google had unlawfully acquired and maintained monopoly power in two open-web advertising technology markets and had unlawfully tied its publisher ad server to its ad exchange.
The judgment did not declare the original purchase itself unlawful.
Its significance is subtler and more troubling.
Infrastructure acquired through one apparently acceptable transaction became part of an architecture whose later operation was found to violate antitrust law.
A regulator examines an acquisition as an event. Society eventually experiences it as a system.
That distinction matters because corporate power rarely resides in one service alone.
Search directs attention. Advertising helps determine which attention can be converted into economic survival. Chrome shapes how much of the web is experienced. Android sits beneath the device in billions of pockets. Play Services mediates much of what happens upon it. YouTube occupies an extraordinary position in public video. Maps increasingly mediates how we understand and navigate physical space.
Each position matters on its own.
Joined together, they begin to resemble something closer to private governance: not government by decree, but governance through defaults, rankings, standards, compatibility, visibility and friction.
No parliament needs to pass a law telling us which application to install, which website to discover, which route to travel or which service will work properly.
Architecture can accomplish a great deal without ever issuing a command.
From Stewardship to Permission
The old phone returned me to Android, and Android returned me to the question of permission.
Google bought Android in 2005 and promoted the operating system as an open alternative in the emerging smartphone market.
Some of that openness remains real.
The Android Open Source Project still exists. LineageOS exists because Android’s source can still be adapted into an operating system beyond Google’s own applications and services.
The escape route is built from the remains of the original promise.
Yet the Android most people encounter is not an abstract open-source project. It is a certified device bound into Google Play, Google Play Services, Play Protect, account systems and increasingly elaborate tests of software and device integrity. An application may be technically compatible with Android while depending upon Google’s surrounding machinery to behave as expected.
Google’s emerging developer-verification system makes the tension visible.
The company argues, with reason, that fraud, impersonation and malware are real, and that knowing who stands behind an application can protect users. Its new verification requirements begin taking effect on certified Android devices in selected markets from September 2026, with broader rollout planned from 2027.
Following criticism, Google has preserved an advanced route through which knowledgeable users can choose to install software from unverified developers. That route requires a one-time setup designed to resist coercion and social-engineering scams, including developer mode, reauthentication and a 24-hour waiting period. Installation through ADB remains available outside that verification requirement.
That softens the original danger.
It does not dissolve the political question.
If the owner of a certified phone must pass through a route designed and permitted by Google in order to install software Google has not verified, then choice survives — but it survives inside Google’s architecture.
The gate is open. Google still owns the gate.
Safety and control have always been close relatives.
The question is not whether protection is necessary. It is who protects whom, from what, and who acquires power through the act of protection.
What, Precisely, Did I Buy?
The language of modern technology encourages us to call ourselves users.
It is a revealing word.
A citizen possesses rights. An owner possesses an object. A user occupies a conditional relationship with a service somebody else controls.
Increasingly, modern technology asks us to purchase in the language of ownership while living in the reality of access.
When the object in my hand can be altered remotely, deprived of compatibility, denied applications, or made dependent upon accounts and servers I do not own, the distinction between owner and user begins to blur.
This does not mean every restriction is illegitimate.
A phone connected to other people and networks is not a hammer. Security failures spread. Stolen identities have victims. Malicious software can empty bank accounts, expose private lives and turn devices into instruments against others.
Absolute freedom without consequence is not a serious social principle — for individuals or institutions.
But neither is permanent corporate authority disguised as consumer care.
If responsibility accompanies freedom, it cannot reasonably be demanded only from the person holding the device while institutions controlling the infrastructure remain beyond the same moral principle.
Ownership worthy of the name should include a meaningful right to repair, alter, maintain and repurpose an object — alongside responsibility for the consequences.
It should not require an ordinary person to become a software dissident merely to give a five-year-old phone a second life.
The promised world of Everyman did not disappear.
It was enclosed around us.
And the company that once seemed to place the world within ordinary reach became the behemoth devouring not our bodies, perhaps, but our choices, our attention, our privacy, our independence, and finally our understanding of what ownership means.
The Gatekeeper Will Index This
I may still install LineageOS on the old Samsung.
I may replace familiar applications with open-source alternatives, use an independent app store, and see how much ordinary digital life can be reclaimed without asking Google to organise it for me.
It will not overthrow a monopoly.
It will not dismantle an advertising market or restore every startup that disappeared into a larger company.
It may not even make the phone more convenient.
Resistance rarely begins by becoming more convenient than obedience.
But perhaps resistance does not always begin with revolution.
Perhaps sometimes it begins with an old phone, a factory reset, and the small, unfashionable insistence that ownership ought still to mean something.
And once this essay is published, it will enter the same machinery it questions.
Google may crawl it, index it, summarise it, and place it before readers according to rules neither writer nor reader can see.
The behemoth may help distribute the essay about the behemoth.
There are few greater signs of power than becoming the principal means by which criticism of your power is discovered.
A. J. Ashé
In:Significant World · 2026
References & Footnotes
1. AOSP and the original promise of openness
Google’s own Android Open Source Project documentation describes AOSP as being designed so that no single industry player becomes a central point through which another player’s innovations can be restricted or controlled. That founding principle sits in striking tension with the increasingly mediated routes through which software can be installed on certified Android devices.
2. On gradual enclosure
The staged introduction of Android’s developer-verification system offers a contemporary example of the essay’s broader argument: changes in control may accumulate through successive adjustments to access, procedure and default expectations rather than through one obvious moment of closure.
3. ADB — Android Debug Bridge
ADB is a command-line tool that allows a computer to communicate directly with an Android device. Google currently states that ADB installations do not require developer verification and are not affected by the advanced-flow waiting period.
References
Android Open Source Project — AOSP overview — Google / Android Open Source Project. Source
Android developer verification — Frequently asked questions — Google / Android Developers. Current guidance on rollout, advanced flow and ADB. Source
Android developer verification: Balancing openness and choice with safety — Google / Android Developers, 19 March 2026. Source
Federal Trade Commission Closes Google/DoubleClick Investigation — Federal Trade Commission, 20 December 2007. Source
Department of Justice Prevails in Landmark Antitrust Case Against Google — US Department of Justice, 17 April 2025. Source
Memorandum Opinion — U.S. and Plaintiff States v. Google LLC — US District Court for the Eastern District of Virginia / US Department of Justice, 17 April 2025. Source
Acquisitions and antitrust — Google Public Policy Blog, 15 December 2010. Includes Google’s account of the Keyhole and Android acquisitions. Source
15 milestones, moments and more for Google Docs’ 15th birthday — Google, documenting Writely’s evolution into Google Docs. Source
Google Analytics / Urchin historical material — Google Analytics. Urchin was acquired by Google in 2005 and became the basis of Google Analytics. Source
Google Maps and Waze, outsmarting traffic together — Google, 11 June 2013. Source
Google DeepMind: Bringing together two world-class AI teams — Google, 20 April 2023. Source
Google completes Fitbit acquisition — Google, 14 January 2021. Source
Editorial note: This essay distinguishes sourced factual claims from editorial interpretation. Informed correction, additional context and professional commentary are welcomed as part of the continuing conversation.