There is a class of software on the internet that pretends to be broken, and it is having a quiet moment in 2026 because most products now refuse to feel broken on purpose. A small set of Google tricks live in this category, and the black hole is the most violent of them. You type four words into the search bar, hit enter, and a singularity opens somewhere on the results page. The links do not fall. They drift sideways, stretch as they move, and disappear past the edge of the screen one by one. A counter at the top of the page tells you how much has been swallowed. None of that is a bug. All of it is the product, and the reason it has survived is that the engineering culture behind it chose to leave the rough edges in.
The pattern matters because it shows what older software used to do that newer software has stopped doing. The black hole was built by a team that bet on the user being curious. They shipped a control surface labeled like developer variables. They left a counter at the top formatted like a Python memory call. They added no onboarding, no tooltip, no confirmation modal, and no graceful empty state. The trick just runs, and the user figures it out by playing with it. That is a small bet, and it is the kind of bet most modern product teams have stopped being allowed to make.
The gc.collect() counter is a quiet argument against product polish
The counter at the top of the page is the part most people screenshot. It tracks how many page elements have been pulled into the singularity, how many are still orbiting, and what the current gravitational mass is. The format reads like the kind of status line a developer would leave in a console window. It is not interactive. It is not branded. It does not have a friendly label. It is a piece of developer voice sitting in a consumer product, and the team that built the trick chose to leave it that way.
That choice is a small argument against product polish. A normal 2026 product team would have asked for a percentage display, a progress bar, a friendly counter with a “you’ve eaten X links” label, or all three. The team that built the black hole did none of that. They shipped the counter in the format that was easiest to write, and they trusted the user to figure out what it meant. The result is a piece of software that feels honest in a way polished software has stopped feeling.
The same pattern shows up across the rest of the trick. The two sliders are labeled mass and spin, not “light / heavy” and “still / rotating.” There is no preset for “polite mode.” There is no animation easing curve designed to make the destruction feel cinematic. The system just runs the physics, and the physics look the way physics look. That is the whole product, and the whole product is the point.
The trick runs in phases and the user figures out each one
The black hole has a lifecycle that the user has to discover on their own, which is one of the more interesting product choices in the trick. There is no tutorial, no tour, no “next step” prompt. The user has to figure out that the page elements can be relocated by clicking anywhere on the screen, that mass and spin are real parameters with real effects, and that there is a button at the top of the page that injects a fresh batch of elements once the original page is gone.
Each of those discoveries takes about thirty seconds to land, and the user has to make them in some order. Some users find the relocate trick first. Some users run the mass slider all the way up and watch the page disappear before they realize there is a feed button at all. Some users never find the feed button and assume the trick is broken after the first minute, which is exactly the kind of confusion the trick is designed to produce.
That lifecycle is the part most product reviews miss. The black hole is not one trick. It is a system that has a discovery phase, a play phase, a quiet phase, and a return phase. Most one-off animations do not have a return phase. The black hole does, and the return phase is what makes it survive multiple visits instead of one. The team that built it did not write a spec for any of those phases. They just shipped the physics and let the user find the rest.
The trick has no sequel and that is the design constraint
The black hole is not the only Google physics toy, and the family is small enough that you can list all of them. Each trick covers a different flavor of destruction, and none of them are sequels to each other. The gravity trick drops everything onto the floor. The floating trick sends everything upward. The thanos snap removes half the page at random. The fan blows everything outward. They are siblings, not versions of each other, and the search bar treats them the same way.
Surviving as a family is what happens when no member of the family has been “improved” into a sequel. Each trick is one page, one trick, one reset button. There is no “google black hole 2” and no “google black hole 3d” because the team has been disciplined enough to leave the trick alone. That is the design constraint the family lives under, and it is the constraint that lets the user feel like they found something instead of being shown something.
The same constraint is why no member of the family has a companion API, a settings panel, or a mobile version. The trick only works on the actual Google search page on a desktop browser, and it only works because the search bar still behaves like a search bar. Anything that would make the trick easier to access would also make it less of a discovery. The team has accepted that tradeoff, and it has kept the trick alive for over a decade.
Trade-offs
The black hole is a small product, and most of the trade-offs are about what is missing.
- No mobile version: the trick does not work on phones, because the desktop browser is where the search bar still behaves like a search bar. Anyone trying to share the trick on mobile will be confused.
- No settings panel: there is no way to save a preferred mass and spin, no way to swap the counter for a different label, no way to record the final frame. The control surface is exactly what the team shipped ten years ago.
- No companion API: you cannot embed the black hole in your own page, hook it into a script, or trigger it from a URL parameter. The trick only works on the actual Google search page, which is what makes it feel like a discovery instead of a feature.
- The discovery is unguided: users who do not find the feed button assume the trick is broken after the page is empty. The team has accepted that confusion as part of the product, and the user has to live with the cost of not finding the return phase.
What I would tell past me
The black hole is the kind of small software product most engineers wish they could ship. Cheap to build, weird enough to remember, and good enough to survive multiple visits without anyone trying to “improve” it. The lesson is not about black holes. It is about the discipline of leaving a finished thing alone once it is finished, and trusting the user to find the return phase on their own.
If you have not tried it yet, open a desktop browser, type the four words into the search bar, and crank the mass slider up. Click anywhere on the screen to move the singularity. When the page goes quiet, look for the button at the top. That is the whole product, and the whole product is the point.