I like software with a clear reason to exist: a missing search feature, an interface that breaks on small screens, or a workflow that needs less friction. My strongest public work combines React, TypeScript, responsive design, and browser-native APIs.

A Firefox add-on that makes long GitHub Stars lists searchable by repository name and description.

• Why: GitHub Stars become difficult to use once the saved list grows.
• Built with: React · TypeScript · Primer React · Parcel · WebExtensions Manifest V3
• Shipped as: A published Firefox add-on with public source and multiple releases

A responsive product-feedback dashboard for scanning, filtering, and sorting requests across screen sizes.

• Why: Dense feedback data should stay understandable on desktop, tablet, and mobile.
• Built with: React · TypeScript · Tailwind CSS · Context · Vite
• Includes: Category filters · Four sorting modes · Responsive feedback cards

My portfolio is also a working interface project: detailed case files, responsive layouts, keyboard navigation, and small interactive labs.

_{Automation-ready examples · replace these with verified updates.}

• EXAMPLE · Project release — Replace with a verified release title, one concrete outcome, and its link.
• EXAMPLE · Portfolio update — Replace with a substantial case-study or interface update and its link.
• EXAMPLE · Merged work — Replace with a meaningful merged pull request or repository milestone and its link.

Core: React · TypeScript · JavaScript · HTML · CSS · Tailwind CSS

Browser and build work: Firefox WebExtensions · Vite · Parcel · Primer React

Also use: Redux · Node.js · MySQL · MongoDB · Figma · Git · Bash

• Start with the friction. I define the confusing moment before choosing the component.
• Design the states. Focus, loading, empty, error, success, and small-screen behavior are part of the feature.
• Ship, test, refine. A polished interface is built through iteration, not decoration added at the end.

• Making browser extensions feel native to the sites they improve
• Building accessible React interfaces that remain clear under responsive pressure
• Improving project documentation so the decisions are as inspectable as the code

🎮 Engineering side quest — Pekka Kana 2: Greta

I also contributed focused C++ and SDL2 work to an existing platformer fork, including quick-save/load controls, rendering improvements, and Windows release packaging. The original project and upstream work are fully credited.

Have a useful product idea, a front end that needs more clarity, or a browser workflow worth improving?

Explore my portfolio · Email me · Connect on LinkedIn

SIGN THE SIGNAL LOG
_{Guestbook URL placeholder · replace it after creating the GitHub Discussion.}

The tidy part ends above. Down here: neon streets, old-web relics, too many tabs, and ideas that have not learned to behave.

_{The web is still awake somewhere.}

_{frequency locked · curiosity online}

OPEN SIGNAL ARCHIVE · console and signal spill

_{clean build on one screen · questionable idea on the other}

signal spill:

_{connection kept alive by curiosity}

ANOMALY 04
_{TAB GEOMETRY EXCEEDS DISPLAY CAPABILITIES
ATTEMPTING FOUR-DIMENSIONAL RECOVERY…}

_{one unstable tab · zero user action required}

ONE IMPOSSIBLE TAB REMAINS

_{you are not lost · the map is just honest}

CARRIER LOST · CURIOSITY REMAINS
_{03:31 PKT ░▒▓}

AUTHORIZED EXITS

_{guestbook exit activates after its Discussion URL is installed}

Portfolio · Featured projects · Email · LinkedIn