The November marathon to the store

By Georg Malahov

Woke up in the middle of the night, checked my email first thing — and there was the confirmation from Google that my extension had been accepted and published for testing by trusted users. Congratulations, review passed. And a wave of real excitement hit me — even though it was just a technical check: no sales, no users, nothing. But I'd been working toward that night for a long time, and the thing I'd been waiting for had finally happened. The night before, by the way, I'd had strange dreams — my head was chewing it all over, I guess.

After that came a fairly draining marathon of getting everything into shape. The way I see it, the production side — auth, lead forms, payments — was one of the biggest things that had to be built at all, and I closed it. What's left now is tidying up the interface: cut the extra buttons, keep two tabs in the sidebar instead of three — transcript and AI chat — add proper onboarding, draw up marketing screenshots. Stripe, though, I couldn't get set up quickly — so I pushed it to the next iterations. And I'd wanted to bring in my test users, let real people poke at it: I sent the link to a friend — and he couldn't install the extension. Turned out I just had to add his email to the test-user list in the Chrome Web Store; I did, and everything worked right away. The fix itself takes a couple of minutes, but a couple of hours went into ironing out these launch-and-test-user quirks.

Somewhere in those same days I had a conversation I'm still turning over a bit. An acquaintance offered to come into the project together, a fifty-fifty partnership. And I said no — not over the share. What got me was something else: he said I had little experience in product vision and marketing — exactly the things I'm taking the course to learn — and offered to take marketing, design, and the product side on himself, leaving me the development. That's what made it a firm no: essentially I was being offered to be just a developer again, with a manager telling me what to do and how. And I want the opposite — to walk the whole path myself, from product to promotion, and learn it hands-on. Maybe that's the wrong call speed-wise — two people would be faster — but the decision is deliberate, so there's no point agonizing over it.

Meanwhile the positioning question keeps circling in my head the whole time and won't let go. The product's main function is to record and save a conversation so it doesn't get forgotten. Everything else — analysis, summary, chat over the transcript — is add-ons, and they should probably be hidden rather than shown off. Because faced with a Swiss army knife, people get lost: there are lots of features, and the value of each one gets diluted. Show one clear thing — "this is so you don't forget conversations" — and at least they understand what it's for. For now it's only a hypothesis; I'll test it on the landing page.

In the small-but-important column — my homework for the marketing and research block finally got accepted. I was as happy as a student who finally got a pass, even though it's just a checkbox in the course. But for me it means the landing page can be built on an already-approved structure instead of guesswork. I updated the homepage following the table we'd gone through, wired in a free API for image optimization, checked robots.txt and the sitemap, refreshed the screenshots. Boring work I used to run away from, and now I do it — and I think I'm even starting to understand why.

Another frame from the same set for the Chrome Store listing: the full-screen transcript view with summary and chat.

The plan for the coming weekend is concrete: tidy up the interface, send it to Google for review on Sunday or Monday, open the page publicly. After launch I want to be doing only promotion and collecting feedback, not endless code. I'm holding myself to a deadline — end of November, start of December, the product has to be in the store.

By the start of December the extension has to be publicly available in the Chrome Store — so that any stranger can find it, install it, and go through the whole flow up to payment. Not "almost ready," but actually available. If by that point I'm fixing small bugs again instead of publishing, it means I've gotten stuck in perfectionism once more, and I'll have to pull myself up short.

Off to cut the extra buttons.