App Portfolio

The projects behind the Petko Dev name

This page is meant to explain the projects, not only launch them. I want each app to have enough context that a visitor can understand its purpose, the design choices behind it, and the kind of improvement work still ahead.

Original work

These projects were built as personal software ideas and learning projects. They are not generic templates copied into a portfolio just to fill space.

Practical goals

Each app starts with a very direct use case: check the weather quickly, manage tasks with less friction, or solve a currency-related everyday need.

Ongoing iteration

I treat each release as part of a longer learning process. Feedback, bug reports, and usage patterns help me decide what deserves the next improvement cycle.

Weatherly artwork
Weather app JavaScript Responsive design

Weatherly

Weatherly is my attempt to keep a weather app simple, readable, and friendly. Many weather interfaces overload the user with panels, ads, and too many competing data points. I wanted a version that feels lighter and more direct.

The project gave me room to practice search flow, visual hierarchy, and the balance between design personality and utility. It also helped me think more carefully about what users need immediately and what information can stay secondary.

  • Main idea: let people check the weather quickly without visual clutter.
  • What I learned: data-driven apps feel better when the interface makes state changes obvious and calm.
  • What still matters: polish, consistency, and continuing to simplify the user journey.
Listly icon
Task manager Gamified UX Frontend project

Listly

Listly is a small task app built around the idea that simple feedback can help people stay engaged. I wanted it to feel lighter than a full project management tool while still giving the user a sense of momentum and reward.

The most interesting part of this project is not the technical complexity. It is the UX question behind it: how much structure helps users, and when does structure become noise? That question pushed me to keep the interface focused and approachable.

  • Main idea: support daily task tracking without making the app feel heavy.
  • What I learned: even tiny productivity tools need strong pacing and clear states.
  • What I want next: continue refining the feeling of progress and completion.
Petko Dev logo card
Currency utility Calculator Practical tool

Euro to Lev and Change Tools

This utility project is built around a very concrete use case: quick conversion and simple change calculations. I like making tools like this because they force me to focus on clarity, speed, and helpful defaults instead of extra decoration.

Practical tools may look smaller than broader apps, but they are useful for improving precision. If a calculator confuses the user, even once, the whole product loses trust. That makes utility projects great training for interface discipline.

  • Main idea: solve a common task with minimal friction.
  • What I learned: utility interfaces need very clear labels, states, and edge-case handling.
  • Why it belongs here: it shows how I approach focused product design, not just large feature sets.

What connects these apps

Although the categories are different, the projects share the same goal: keep the experience understandable and useful. I prefer apps where the value is visible quickly and the interface supports the task instead of distracting from it.

That is why I document them here in a single portfolio. They show a consistent approach to building, even when the features are very different.

What visitors should expect

Some projects are more polished than others, and that is normal for an active portfolio. I would rather show real work that is evolving than hide everything until it looks perfect. What matters is that each project is real, functional, and explained honestly.

If you want to help shape future versions, the contact page includes ways to send feedback or join beta testing.