I build software from the first idea to a stable release, testing and improving it at every step.

I've worked in IT for over a decade and I've seen products from every side: the first idea, the requirements, the code, the bugs and the support tickets after launch. These days I do all of it myself, with AI tools handling the slow parts. Since June 2026 that's meant an Android app, a Windows desktop app, a Chrome extension and a stack of web apps and games. Everything below exists, and most of it you can open right now.

9projects shipped in 2026
1,154commits across these projects
4platforms: Android, Windows, web, Chrome
11years working on the web

01 / Work

Things I've built

Five I'm proudest of first. Each project has its own page with what it does, its activity on GitHub and a changelog. The changelog page has every release of every project in one list.

AI Hive v0.55 5h 42%
A mock-up of four agents working on HiraKataQuest at once. They check the shared board before touching a file.

Windows desktop app

AI Hive

A control center for running many AI coding assistants side by side. Each tile is a real Windows pseudo-console running Claude Code, Gemini, Grok or a plain shell. It's the workbench I built to keep several workstreams moving at once.

  • ~86k lines of Python
  • 777 commits
  • PySide6 + ConPTY
Automation Test Platform run history: nine runs across Playwright, Cypress and Selenium with pass, partial fail and fail statuses, results and fail rates

QA platform

Automation Test Platform

One dashboard to run Playwright, Cypress and Selenium suites against any site, watch every test live and keep the history. The QA tooling I always wanted, built on my own time.

  • 3 frameworks, one view
  • Suites × sites run matrix
  • HTML + PDF reports
HiraKataQuest library: every hiragana tile tinted from red to green by its average score HiraKataQuest writing screen: the kana あ traced on a grid, scored 99 with Excellent form

Android app

HiraKataQuest

Learn to read and handwrite hiragana and katakana, as single characters or whole words. You trace the handwritten form on a genkouyoushi grid, watch the stroke order play out, and get a score on what you actually wrote.

  • ~29k lines of Kotlin
  • 168 commits
  • v0.4.0 released
Ironlog workout log on a phone: squat, bench and deadlift sets with volume and top set totals Ironlog plate loader on a phone showing a 125 kg barbell loaded with red plates

Web app

Ironlog

The powerlifting tracker I train with. It logs sets, works out which plates go on the bar and counts macros, all stored in your browser with no account.

  • 47-lift library
  • 92-food pantry
  • React + TypeScript
One More Tile puzzle board with fill-a-pix clues, sudoku patches outlined in gold and picross patches in teal

Browser game

One More Tile

A cross-stitch puzzle that hides a pixel-art painting. Fill-a-pix, sudoku and picross share one canvas, and every region you finish reveals a piece of the picture.

  • No build step, no install
  • 119 commits
  • Co-op for up to 4

More projects

02 / Process

How I build

I've sat in every seat a product passes through, from the first idea to the support inbox after launch. You get one person who keeps the whole picture in mind, and a modern toolchain that makes it fast without cutting corners.

  1. 1

    Start with the problem

    Before any code, I want to know who it's for, what they're trying to do and what would make them come back. A good idea survives those questions. A weak one gets fixed cheaply, on paper.

  2. 2

    Agree on what done looks like

    What it has to do, what it won't do, and how we'll check it works. All of it written down and agreed before the build starts, so nothing at handover comes as a surprise.

  3. 3

    Build in short loops

    Work is split into small, parallel tasks, with AI-assisted tooling doing the heavy lifting. You see real progress mid-build, and your feedback goes straight into the next loop, not a list for later.

  4. 4

    Test it twice

    Testing has been my day job for years. Automated tests run on every change, and AI Hive's suite alone makes over 4,000 checks. Then I use it myself, on real devices, the way your users will. Green tests catch regressions. They don't catch a confusing screen.

  5. 5

    Ship something you can open

    A link that plays, an APK that installs, an extension that loads. If it only runs on my machine, it isn't done.

  6. 6

    Listen after launch

    Release is where the real feedback starts. Years in support taught me to talk to the people using the thing, find what confuses them and turn that into the next round of work.

Mario Molnar laughing in a white shirt

03 / About

Hi, I'm Mario.

I've been in IT for eleven years, and somewhere along the way I've sat in every seat a product passes through. I've been in the meeting where an idea first came up and helped turn it into requirements. I've tested features while they were still half-built, sent them back to the developers and tested them again. I've organized the work so the team knew what came next, and held the designer's mockups up against the real front end to find where the flow drifted. I've run the last checks before a release, and afterwards I've answered the users who wrote in with questions and bug reports.

That's the part I value most. I know which shortcuts come back as tickets two weeks later, and what a person will try in the first minute with something new. Building my own products means I play all of those parts now. I still write the requirements before the code, and every build goes through rounds of testing and fixes before it ships.

  1. 2015Started on the web, building data scrapers
  2. 2017Technical support engineer
  3. 2023QA engineer
  4. 2026Building products end to end

Away from the keyboard

595kg

Powerlifting. Competing since 2019, with a 595 kg best total across squat, bench and deadlift. Yes, that's why Ironlog exists.

35

Countries backpacked. Night trains, hostels and whatever the locals are eating. I'd rather live like someone from the place for a week than tick off landmarks, and it's taught me to adapt fast and keep calm when plans fall apart.

Languages. Romanian and English fluently, some German, and beginner Japanese, which is how HiraKataQuest started.

04 / Contact

Have something you want built?

A tool for your business, a prototype, a game idea, or a test suite for something you already have. Tell me what it should do and I'll tell you honestly whether I can build it.

Email me

molnarmarioandi@gmail.com

Gmail Outlook Yahoo Mail Your mail app
WhatsApp

Or find me on GitHub. Based in Romania, working remotely.