Real projects, not placeholders
Every featured app on this site is something I have actually built, tested, and published or shared. I care about showing the practical use of the project instead of inflating it with empty claims.
Independent Developer
I build small, useful apps and document the work honestly.
I am Petko Karov, also known as Petko Dev. This site is the public home for the apps I build with HTML, CSS, and JavaScript, the experiments I keep improving, and the lessons I learn while shipping them.
Instead of using this portfolio as a simple launcher page, I want it to explain what each project does, who it helps, what I learned from building it, and how people can try new versions or join testing.
Why this portfolio exists
I wanted a place where visitors can understand the thinking behind my work. A useful project is not only a button that opens an app. It also includes the problem it solves, the tradeoffs behind the interface, and the improvements planned for the next version.
Short feedback loops
I like small apps because they let me learn fast. I can release an idea, watch how people use it, collect notes, and make the next version better without waiting months to see results.
Clear communication
This site is also a communication tool. It should help someone understand what I build, how to contact me, what I am working on now, and what kind of feedback is most helpful.
Featured work
These are the projects that best represent the kind of software I enjoy making: focused, easy to understand, and useful without requiring a long learning curve.
Weather
Responsive UI
JavaScript
Weatherly
Weatherly started as a clean way to check the weather without clutter. The goal was to keep the interface friendly and fast while still showing the information a user cares about first.
It helped me practice input flow, weather data handling, light visual branding, and the difference between a demo that works and a product that feels polished.
.png)
Productivity
Gamified Tasks
Frontend
Listly
Listly is my lightweight task manager for people who want a simple system and a little momentum. It is intentionally small so the user spends more time finishing tasks than managing them.
This project pushed me to think more about motivation, pacing, and the balance between playful design and practical productivity.
Utilities
Local Use
Problem Solving
Practical converters and experiments
Not every useful app needs to be large. Some of my projects are focused tools built for a specific task, such as currency conversion and change calculation. These projects help me sharpen clarity and reliability.
They are also a good reminder that developer portfolios should show thinking, not just features. A small tool can still say a lot about how a developer approaches real users.
How I approach building
I am still growing as a developer, so my process is intentionally simple: build something real, learn from it, improve the next version, and keep documenting the work. That makes the portfolio honest and keeps the learning visible.
What matters most to me
- Fast loading pages and straightforward navigation.
- Interfaces that are easy to understand on mobile and desktop.
- Project pages with enough explanation that a visitor can see the value before opening a demo.
- Clear feedback channels for bug reports, tester notes, and release ideas.
What I am improving next
- Stronger project documentation around each app and why it exists.
- More release notes and behind-the-scenes updates for returning visitors.
- Better case studies that explain decisions, not only finished screens.
- A more complete content library so this site works as both a portfolio and a learning journal.
Main featured projects
Each one solves a different kind of everyday problem, from planning tasks to checking weather to handling simple conversions.
Years studying programming
The site reflects an ongoing learning process built around practical frontend work and real published experiments.
Current portfolio refresh
The site content is being expanded so visitors can understand the projects before they click into any app or external store listing.
Frequently asked questions
These are the things people usually want to know first when they land on a developer portfolio that includes both projects and playable demos.
What kind of developer work do you focus on?
I focus on frontend projects and lightweight web apps built with HTML, CSS, and JavaScript. I enjoy tools that solve a clear problem without becoming heavy or confusing.
Are the apps on this site real projects?
Yes. The featured apps are real projects that I have built and shared. Some are published more formally, while others are portfolio experiments or in-progress utilities that help me test ideas and improve my workflow.
Why include project writeups instead of only demo links?
A demo shows that something opens. A writeup shows why it matters. I want this site to explain the intent, design choices, and future direction behind each project so visitors understand the work in context.
Can I test new versions or send suggestions?
Yes. The contact page includes an email address, a Telegram option, and a beta tester form. I welcome practical feedback, bug reports, UI suggestions, and notes about what feels confusing in the current versions.