The problem
The existing NNS dapp did a lot. That was useful for experienced users, but the same scope made it hard to simplify without disrupting workflows people already depended on.
I proposed a separate governance app. The goal was not to replace everything at once. It was to create a simpler path into staking, voting, delegation, accounts, and rewards.
What we tried first
I built a quick AI-assisted prototype in an internal repository. It was deliberately disposable. We used it to make the idea tangible, test flows with stakeholders, and decide whether the direction was worth pursuing.
For production, we started again. I wrote the architecture documentation and the first reference code, then set up CI, tests, type checks, human review, and a local QA environment. The production app used a modular React and TypeScript frontend with Rust canisters on the Internet Computer.
My role
I proposed the product and became its main point of contact. I led the frontend direction and worked across product decisions, backend delivery, tooling, security, documentation, and releases as the team became smaller.
This was still team work. Other frontend and backend engineers contributed to the product, reviewed the canister work, and helped shape the implementation.
What changed
We released the first production version in January 2026 and announced it publicly at the end of February.
From 27 March through 22 July 2026, the app recorded 46,624 unique visitors from 150 countries. These are Plausible visitor figures, not authenticated users or customers.
The useful lesson was simple: the prototype and the production app had different jobs. One helped us learn quickly. The other needed to be understandable, testable, and safe to operate.