01. Notice
A project usually starts with a question, a friction point or a mechanic I want to understand.
ARSENII DOROGIN • INDEPENDENT DEVELOPER
I build apps, games and small experiments in my spare time.
This is where I document what I make, the tools I explore and what each project teaches me along the way.
What I explore
My projects move between native apps, playful systems, interfaces and backend logic. Each one is a reason to understand another layer a little better.
Swift and SwiftUI experiments shaped around touch, small screens and the character of Apple platforms.
Responsive layouts, interaction details and visual systems that make complex ideas easier to understand.
Progression, resource loops, state management and the small rules that make a game feel coherent.
APIs, persistence and data models that support the visible experience without getting in its way.
Small tools, scripts and AI-assisted workflows for removing repetition and exploring new interactions.
Taking a personal project from an early build to something others can try, then learning from feedback.
Games, apps and prototypes made independently in my spare time. Each card is clear about what exists today and what is still an experiment.
I keep the loop intentionally simple: make a small version, use it, notice what feels wrong and improve the parts that matter.
Browse the projects →A project usually starts with a question, a friction point or a mechanic I want to understand.
I reduce the idea to its smallest useful loop and test whether it is interesting enough to keep going.
Interface, data and underlying systems evolve together in small working versions.
I publish when it makes sense, collect feedback and write down what the project taught me.
I'm Arsenii, an independent developer based in Spain. AVSIDEV is the name I use for the apps, games and software experiments I build in my spare time.
I enjoy moving between interface details, application architecture, game mechanics and backend logic. Building a real thing is how I learn what the idea actually needs.
Each project begins with something I want to understand through making.
Small usable builds reveal more than a long list of imagined features.
Reflection and iteration are part of the project, not cleanup at the end.
I choose tools around the thing I want to learn or build, then keep the stack as small as the project allows.
Write to me about one of the projects, something you are building, or a technical idea you would like to compare notes on.