Prism: extension aur site

Problem

Ek solo ecosystem ship kar sakte hain, toh use luck bhi keh sakte hain; lekin dusra solo ecosystem ship karna ek process hai. Prism, ek site aur browser extension, ko banaya gaya tha taaki repeatable part ko prove kiya ja sake: idea → product → shipped, bina team ke aur bina ek saal ke.

Decisions

Playbook ko reuse karo, code nahi. Ueue se sikhe hue lessons ko carry over kiya: surface-per-strength, ruthless scope, states as features. Lekin Prism ne apne technical calls ko alag se liya jab product ne alag calls maange.

Extension-first. Prism ka value browser mein hai, toh extension hi product hai aur site uska front door hai, doosra nahi. Is ordering ne sab kuch decide kiya: onboarding wahan hota hai jahan value hai, aur site click bechti hai, scroll nahi.

Ship, phir sharpen. Pehla public version jaldi release kiya, phir real usage ke against iterate kiya, imagined users ke against nahi.

Outcome

Prism live hai end to end: extension Chrome Web Store mein, site production mein. Dusra ecosystem pehla se jaldi ship hua, playbook sahi tha, jo hypothesis tha. Jo Ueue ne possible prove kiya, Prism ne repeatable prove kiya.