1 item
Import locale packs. Fill App Store Connect. Packpour turns multilingual app metadata from one file into ten filled locale pages on App Store Connect — without ever clicking Save, Publish, or Submit for Review for you. ────────────────── WHAT IT DOES ────────────────── App Store Connect asks you to fill Promotional Text, Description, Keywords, and more, one locale at a time. Packpour reads a structured TXT or Markdown pack that contains every localized value you already wrote, picks the pack matching the page's current locale, and pours each labeled value into the matching editable field. Typical flow: open the metadata page, open the Packpour side panel, click "Fill App Store Connect page." Review the result, then you press Save. Packpour never submits for you. ────────────────── KEY FEATURES ────────────────── • One pack fills many fields — import a single TXT or Markdown file and every labeled value lands in the right field on the current locale page. • Smart field matching — tries label text, placeholder, aria-label, name, and id. Falls back to focused-field fill when detection misses. • Import many locales at once — drop in multiple files; their file names become your locale switcher (en, zh-CN, zh-TW, ja, ko, fr, de, es, pt, it, and more). • Keyword byte-limit tracking — see the 100-byte keyword usage live. • Focused-field fallback — if a field doesn't auto-match, click into it and fill just that one. • 10 UI languages — English, 简体中文, 繁體中文, 日本語,한국어, Français, Deutsch, Español, Português, Italiano. Auto-detects your browser locale; switch anytime in Settings. • Built-in updater — Settings → About → "Check for updates" hits the GitHub Releases API. ────────────────── PRIVACY & SAFETY ────────────────── • 100% local — imported packs live in Chrome local storage. Nothing is sent to any server. • No analytics, no telemetry, no account. • Scoped to appstoreconnect.apple.com only — the content script runs nowhere else. • Password, payment, and token-looking fields are always skipped. • Save, Publish, and Submit for Review are never clicked by Packpour — you stay in control. ────────────────── HOW TO USE ────────────────── 1. Click the Packpour toolbar icon to open the side panel. 2. Import one or more locale packs (TXT or Markdown). A built-in AI prompt template helps you generate structurally correct packs for any language. 3. Open the App Store Connect page you want to fill, pick its locale at the top-right. 4. In Packpour, select the matching pack and click "Fill App Store Connect page." 5. Review the filled fields, fix anything you want, then press Save yourself. ────────────────── WHO IT'S FOR ────────────────── Indie developers and small teams shipping apps into 5–20 locales who are tired of copy-pasting the same metadata structure across dozens of App Store Connect pages. ────────────────── PERMISSIONS, EXPLAINED ────────────────── • storage — to keep your imported locale packs and UI preferences locally. • activeTab / scripting — to fill fields on the App Store Connect tab you have open, only after you click the fill button. • sidePanel — to show the Packpour UI as a Chrome side panel. • host permission for https://appstoreconnect.apple.com/* — so the content script only runs on that domain. ────────────────── OPEN SOURCE ────────────────── MIT licensed. Source, issues, and releases: https://github.com/hooosberg/Packpour Website: https://hooosberg.github.io/Packpour/ Contact: zikedece@proton.me Not affiliated with Apple. App Store Connect and all Apple trademarks belong to Apple Inc.
Apr 23, 2026
rating_count is the Chrome Web Store ratings count, not a written-review count.
Media assets
Screenshots and videos on the listing.
Has promo video
Whether the listing includes at least one video.
Languages
Declared language locales.
Developer website
Listing exposes a developer website URL.
Contact email
Listing exposes a contact email.
Keyword in name
Case-insensitive substring match in the name.
Keyword in description
Case-insensitive substring match in the description.
Keyword occurrences in description
Count of case-insensitive occurrences in the description.
Category user-count percentile
Share of same-category extensions with fewer users (null if unknown).
These are transparent listing completeness / keyword signals, not a prediction of Chrome Web Store search ranking.