Alexey Rodionov

As lead front-end developer, he owns the decisions that decide whether a web product holds up after launch: architecture, framework and stack choices, third-party integrations, client-side security, and performance under real traffic. That is also where Mercury's technical claims come from. When an article compares approaches, quotes a benchmark, or says a platform cannot do something, the test behind it was run in the practice he leads or traced to a primary source he can point to.

Outside Mercury, Alexey is a Chromium contributor. His code ships in Chrome DevTools: CSS property documentation on hover, Baseline status for CSS properties, stricter web app manifest validation, and pointer-event support that made DevTools usable by touch, pen and XR controllers. He added Meta Quest packaging for Progressive Web Apps to Google's Bubblewrap and Microsoft PWABuilder, and the App URI Handler option for Windows packages to PWABuilder. He writes documentation for developer.chrome.com and web.dev, works with the Chrome, Edge and Samsung Internet teams through Chromium's issue tracker, Gerrit and GitHub, takes part in web standards work, organizes the Russian-speaking PWA community, and speaks at conferences.

On the Mercury blog, Alexey writes about the technical side of custom software: how to choose a stack and when to change it, what integrations cost in complexity, where web and native apps actually differ, how to read a code audit, and what browsers and app stores will and will not let you ship.