From the team
Blog
Notes on building Nop — engineering deep-dives, feature write-ups, and why we think native still wins.
Chasing five memory leaks in a week
A native app has no excuse for a growing heap. How we found and fixed a run of leaks in Nop's Capture, History and Collections screens.
Inside the cookie jar
Session cookies are the part of HTTP everyone forgets until they break. Here's how Nop's cookie jar captures, edits and injects them.
The HTTP client for the RAM apocalypse
Why we started Nop: a bet that a native, immediate-mode desktop app can be faster to open and lighter to run than anything shipping a browser inside itself.