Hey everyone. Rafael here, solo founder and builder of Pawly. A few things I want to share that didn't fit in the description: The hardest thing I built: the tab-lock sync system. The pet needs to exist in exactly one tab at a time — but when you switch, it has to "teleport" to its last position on the new page, and if you change the active pet species, all open tabs need to re-render simultaneously without race conditions on chrome.storage. More edge cases than I expected. The thing I'm most proud of: the Canvas accessory renderer. Since the pet's body position varies per animation frame, CSS overlays don't work — I built an AnatomyResolver that stores per-frame anchor coordinates and applies transforms in real time so hats and body items stay perfectly synced regardless of what the pet is doing. It sounds niche but it makes the wardrobe feel polished. What I'd love feedback on: the D1 retention problem. 186 organic installs in 8 days, but only 16% come back the next day. I've added daily quests and a wellbeing system specifically to create a daily return trigger — but I'm curious what you think the right mechanic is for a browser extension that has to compete with everything else on the screen. What's next: new pets (penguin, ferret, more cats and custom pets), more accessories, and the feature I'm most excited about — the pet reacting to the content of whatever page you're on. Opens GitHub → puts on glasses. Opens YouTube → sits down and watches. That one's going to be fun. Thanks for checking out Pawly. Happy to answer anything about the Chrome MV3 architecture, the payment integration, or the design decisions. 🐾

Pawly Extension

A virtual pet that lives in your browser.

A virtual pet that lives in your browser.