Store Manager

Context

My co-founder and I built and shipped Store Manager v1 within February 2026. It's a Chrome extension + web app for app developers and ASO managers, built with TypeScript and WXT, integrating directly with App Store Connect and Google Play Console.

The problem

Managing store listings across App Store and Google Play for multiple apps is painfully manual. Updating metadata across 40+ locales, uploading screenshots per device size, calculating fair pricing per country. All of this had to be done by hand inside native dashboards that were clearly not built for studios or high-volume publishers.

The idea with 14x studio was to make apps available worldwide in a maximum number of languages with correct translation quality. Existing tools solved parts of this problem via CLI, but there was no visual, browser-native layer. We were spending roughly 10 hours per submission cycle just on busywork that had nothing to do with the product itself.

The solution

Store Manager is a Chrome extension that sits directly on top of App Store Connect and Google Play Console, adding an automation and management layer with a visual interface. Core features at launch:

• Bulk metadata upload: update titles, descriptions, keywords across all locales at once
• Bulk screenshot upload: push screenshots for all device sizes in one flow
• Instant translation: auto-translate metadata for all selected locales
• PPP pricing calculator: set fair per-country pricing benchmarked against the Netflix and Big Mac index

The key differentiator was the Chrome extension format: no new login, no separate dashboard to manage, it just enhances the tools developers are already inside.

Outcomes

The extension is publicly available on the Chrome Web Store under 14x.app. Numbers are early, but the impact on our own workflow is the clearest signal: submission time dropped from ~10 hours to ~5 minutes, a 120x speed improvement. As the primary users ourselves, the core value proposition is proven in production. We are currently improving the ASO translation part to allow any team to optimize their store page automatically with AI.

Retrospective

The ICP of this product is a vibe coder or developer working solo or in a small team who wants to automate their store submission but still have an interface to understand what's happening concretely.

To reach them, we tried posting on Twitter (X) to attract indie hackers and solo developers, but we didn't cut through the noise due to a lack of personal branding. We also tried Reddit but got banned quickly after our first posts. We published around 20 posts to have real data to measure whether it worked, and 15 were banned. Distribution through developer communities was harder than expected: posts either got banned or generated low engagement relative to the time invested. We poured significant effort into a channel that didn't pay off.

Learnings

Validate market demand, not just workflow pain. We knew the problem was real because we lived it, but we assumed other developers felt the same pain without ever asking them. Even a week of conversations with other vibe coders or indie app developers before writing code would have shaped the positioning and potentially the distribution strategy.

CLI tools leave a visual gap. The blue ocean was real, but the audience that feels this pain needs to be found deliberately.

Chrome extension discovery is near-zero. The Web Store is not a growth channel the way the Apple App Store can be. Organic distribution is significantly harder to get here.