The first version of the project was only supposed to be a visual toy.
I wanted a little black hole on a page. Not a scientific simulation, not a full game, not a serious productivity app. Just a dark circular object in the browser that could swallow text and make the page feel quieter after it did.
The prompt was simple: type something you never say out loud, press enter, and watch it disappear.
That could have been the whole thing. A text box, a canvas animation, maybe a tiny particle effect. But after I got the visual working, the silence felt unfinished. If the page was asking people to give it an unsaid sentence, the moment after submission needed some kind of response.
So the black hole became a sound tool.
The Original Interaction Was Too Literal
At first, the interaction was almost embarrassingly direct.
You typed a sentence. The sentence moved toward the center. It collapsed into a dark circle. The circle pulsed once. The text vanished.
It worked, technically. But it felt like a delete button wearing a costume.
The problem was not the animation. The problem was that the project had no emotional aftertaste. The user gave the page something private, even if it was only a test phrase, and the page answered with nothing.
That made me rethink the output. Maybe the sentence should not come back as text. Maybe it should come back as tone.
Why Sound Made More Sense Than More UI
A normal developer instinct would be to add more interface.
Show a history panel. Add categories. Let the user tag the thought. Add export. Add sharing. Add a dashboard of swallowed sentences.
That felt wrong for this project.
The whole point was disappearance. If the page immediately turned the input into a database-like artifact, it would undo the mood. I did not want the black hole to become a notes app.
Sound offered a better path because it could respond without explaining too much. A low hum, a soft loop, or a tiny melodic fragment can acknowledge the input without turning it into content.
The Small Workflow I Ended Up With
The project became a three-part browser sketch:
The user writes a short sentence they do not plan to publish.
The sentence visually collapses into the black hole.
The page plays a brief sound response based on the mood of the interaction.
Using AI Audio As A Draft, Not A Decision
The useful shift was treating AI audio as a sketching layer, not as the final author.
For example, if I wanted the page to feel less heavy and more human, an ai birthday song maker could be used as a strange but useful contrast point: take a tool designed for celebration, then study what makes a short generated phrase feel warm, direct, and personal.
For the actual mood bed, an ai lofi generator fit the experiment more naturally. Low-volume lo-fi textures gave the black hole a sense of gravity without making the page feel theatrical.
In both cases, the point was not to outsource taste. The point was to create fast audio drafts that were concrete enough to reject, trim, or reshape.
The Hard Part Was Restraint
Once sound entered the project, it was tempting to overdo it.
A huge bass drop made the black hole feel silly. A dramatic cinematic swell made it feel like a trailer. A bright melody made the private input feel too cheerful. Silence with only one soft pulse worked better than most of the clever ideas.
That became the main lesson: an emotional interface needs less sound than you think.
The audio should not narrate the user's feeling. It should leave room for the user to bring their own feeling to the moment.
What The Black Hole Actually Needed From The Code
The technical side stayed small.
The input field did not need much. The animation needed a believable center point, a smooth easing curve, and a way to make the text feel pulled instead of simply hidden. The audio layer needed volume control, a short fade-in, and a clean stop so repeated submissions did not stack into noise.
The most important code decision was not a library choice. It was refusing to preserve too much.
The interaction felt better when the sentence disappeared completely. No local storage. No list of previous entries. No secret archive. If the project says it is a black hole, it should behave like one.
Where This Kind Of Experiment Is Useful
This pattern is useful beyond this specific toy.
A lot of creative web projects sit somewhere between utility and feeling. They are not exactly apps, but they are not only decorations either. They ask the user to participate, then they need to answer in a way that matches the emotional contract.
Sound can help with that, especially when the response should be felt more than read.
A meditation timer, a private journaling toy, a music mood board, a memory capsule, or a tiny generative poem can all use audio as a soft response layer. But the same rule applies: the sound has to serve the interaction, not announce itself as the feature.
What I Would Change Next
If I kept building this, I would avoid turning it into a big platform.
The next version would probably add only three things: a better visual collapse, a few selectable sound moods, and a local-only privacy note before the user types anything. Even that might be too much.
The best version may be the one that stays small.
A page. A sentence. A black hole. A short sound after the sentence is gone.
The Thing I Liked Most
I liked that the project became harder to describe after sound entered it.
It started as a visual toy. Then it became an interaction design problem. Then it became a small audio workflow. Somewhere in that mess, it started to feel like a real creative coding experiment.
That is usually a good sign.
Small projects get interesting when they stop being one clean category and start asking for judgment across a few different mediums. The black hole did not need more features. It needed the right response after it swallowed something.
In this case, the response was sound.
Top comments (0)