Work / Projects
Building apps, solving problems, experimenting with tech - this is what my work looks like.
What I've Built
I've worked on quite a mix of web and mobile projects over the years, sometimes handling pure development, other times getting pulled into architecture decisions because the system just needed a better structure.
On the web side, I've built full-stack apps with Node.js, Vue.js, and MySQL. In a few retail projects, I had to design the database from scratch and rethink parts of it midway because business rules kept evolving. One of them involved syncing inventory between physical stores and an online platform, which turned out to be more complex than it initially looked. I also worked on several PHP/Laravel projects in the automotive space — mostly internal systems: KPI dashboards, finance tracking, operational tools. A lot of that work was less about flashy features and more about making sure the architecture wouldn't collapse six months later.
For mobile, I've been involved in both iOS and Android projects. In some cases, I handled the early architecture planning and mockups before development even started. Some apps were tightly connected to backend services (Node.js or PHP APIs), while others were standalone tools with integrations like iCloud or Google Drive. I've worked on eDetailing apps for the pharmaceutical industry, where usability and offline behavior really mattered, but also on other types of apps that were more utility-driven.
I've also spent time working with QlikSense, integrating it into custom web applications. Beyond embedding dashboards, I built custom extensions and mashups when the default components weren't enough. That usually meant digging into both frontend and backend layers to make analytics feel less like a separate tool and more like part of the product.
On top of that, I've developed websites and small eCommerce setups with WordPress. Nothing huge — usually projects targeting a few hundred to around a thousand active users. The focus there was practicality: clean structure, easy content management, and systems that clients could actually maintain without calling a developer every week.
Overall, I tend to care a lot about structure and maintainability. I've seen what happens when those are ignored, and fixing them later is never fun. I like solving problems that look simple at first but turn out to have hidden constraints once you get into the details.
Note: All of the work described here is presented in a NDA-friendly way, so no screenshots or detailed visuals of client projects are included.