My name is Vojta Holeš. I am 16, I live in the Czech Republic, and everything you can currently see under the Vyldor name was made by me: the product concept, the website, the 3D model and renders, the engineering notes, the social posts and the emails.
That sentence can sound like a claim about talent. I mean it as evidence about persistence. I have programmed every day for more than two years, and when I decide that something matters I keep working on it. But I have never built hardware before. Vyldor has no physical prototype, no manufacturing partner, no funding and no team. It would be dishonest to hide the gap behind polished renders.
What Vyldor actually is
Vyldor is a smart leather belt designed to let your phone reach you without asking for your eyes. A single mono earpiece docks in the buckle. Two haptic zones sit at the hips. One hidden button confirms anything that matters. The phone does the computing, maps, calls and AI; the belt is the physical interface.
It is deliberately not another miniature phone. There is no screen, no always-on microphone, no SIM and no proprietary cloud that can turn the object into a brick if the company disappears. Pull the earpiece out to start a voice session, return it to stop, feel left or right directions at the waist, and press once to approve an action.
The renders are not proof
A render can prove that a design has been modelled consistently. It cannot prove that the earpiece sounds good, that two vibrations can be distinguished through clothing, that the buckle survives years of load, or that the electronics can be certified. Those are experiments, not images, and none of them has happened yet.
That is why every product image is labelled as a render and every dimension is called a design target. Nothing is for sale. There is no price and no ship date. The point of publishing now is to find the questions that a first-time hardware founder does not know to ask.
Publishing the embarrassing parts
The first earpiece did not fit its own dock. Both measurements were in the specification for weeks and nobody subtracted them. The belt was a closed loop with no way to put it on. The structured data told Google that an unbuilt product was free and available for preorder. The renders were visually polished while contradicting the lighting brief.
Each mistake now has its own engineering note with the numbers, the reason it survived and the change made afterward. Hiding those mistakes would make the project look more advanced for a week. Publishing them makes the next mistake easier for someone else to catch.
What I can build, and what I cannot
I can build the companion application and the product software myself. The funding is not for outsourcing a website or pretending an app is the hard part. It is for the things I cannot responsibly improvise: a functional prototype, electrical and mechanical engineering, acoustics, leather construction, testing, certification, intellectual property work and manufacturing.
Being a solo founder does not mean believing I can do every discipline. It means taking responsibility for finding the people who can do the ones I cannot.
The useful response is criticism
If you build wearables, electronics, audio products, leather goods or certified consumer hardware, I do not need encouragement as much as I need the sentence that begins: this will fail because. One precise objection is worth more than a hundred likes.
The complete status, dimensions and known risks are public. Read them, find the weakest assumption and send it to hello@vyldor.com. If the idea survives good criticism, it becomes worth building. If it does not, finding out before tooling is the best possible result. Read the current design status
I am not asking anyone to believe that a sixteen-year-old has already built a wearable company. I am asking them to judge the work that exists, point at what is wrong, and watch what happens next.