I am Petko Karov, a developer who enjoys building focused web experiences with HTML, CSS, and JavaScript. I learn best by turning ideas into something visible, testing it, improving it, and then reflecting on what worked and what did not.
That is why many of my projects are intentionally practical. A weather app, a task manager, or a simple converter may look small, but each one teaches something important about usability, reliability, structure, and communication.
I like software that is easy to understand and useful right away. I am especially interested in interfaces that remove friction instead of adding it. If a person can open a page, understand it quickly, and get value in a short time, I feel I am moving in the right direction.
I also care about visual identity. Even on small projects, I want the name, icon, and tone of the app to feel intentional and memorable.
This site is more than a homepage with outgoing links. I want it to act as a clear portfolio, a project journal, and a trustworthy place for people to understand the work before they open any app demo or store page.
Each project page should explain why I built the app, which users it is meant for, what I learned, and what I want to improve next. That context matters as much as the code.
I do not want the site to sound bigger than it is. Some projects are polished, some are evolving, and some are experiments. Being clear about that helps the portfolio feel more real.
Good feedback is one of the fastest ways to improve. That is why I keep contact options visible and use beta testing as a way to learn where the app is useful and where it still creates friction.
Clarity first. Users should understand what the page is for without hunting for answers.
Small scope, real value. A compact app can still be meaningful if it solves a specific problem well.
Keep learning visible. Publishing progress helps me stay accountable and gives the work a story people can follow.
Trust matters. Pages should be complete, easy to navigate, and honest about what the project currently offers.
Better case studies. I want each project page to feel like a useful explanation, not only a gateway to the live app.
Stronger release notes. Returning visitors should be able to tell what has changed and why it matters.
Higher quality portfolio content. The site should stand on its own as something worth reading, even before someone launches a demo.
More direct collaboration. I want to grow the feedback loop between building, publishing, and learning from real users.
