Start here
- What is App Publishing Assistant? App Publishing Assistant helps you get ready to publish on the Microsoft Store — organized answers, checklists, and project files in plain language.
- Who is N78-APA for? Anyone who built an app — including with AI or no-code tools — and stalled at developer account signup or Partner Center listing screens.
- Prepare here, publish in Partner Center Prepare store account answers, project folders, credentials, and listing details in N78-APA. Sign up and submit in Partner Center when checklists are complete.
- Recommended setup order Suggested flow: Store Account (optional first) → Project → Repository → Credentials → Microsoft Store listing.
- Using the color-coded checklist Open pages from the View menu. Red rows are not started; green is complete. Pick any row to work that item.
Setup
- Project targets and app name Set intended stores, target devices, listing type, app pricing, default language, and the public app name once.
- Project folder and workspace Choose the folder on your PC that contains your source code. All publishing answers live in a .apa subfolder.
- App pricing model Choose free, one-time purchase, or subscription for your app on the Microsoft Store before listing prep.
- Quick start checklist Shortest path from “I have an app” to validated Microsoft Store listing data ready for Partner Center.
Microsoft Store account
- Partner Center account enrollment Gather individual or company account details, tax and payout profile, and business verification before Partner Center signup.
- Choosing your sign-in email You cannot change the Microsoft account used to sign in to Partner Center later — pick an address you will keep long-term.
- Individual vs company account Pick the account type that matches how you publish. Company accounts require extra business verification.
- Support contact fields Support email, phone, and website shown on Store listings — required for a complete enrollment profile.
Repository & credentials
- Repository and git remote Link publishing metadata to where your app code lives. Remote URL is optional but recommended.
- Default branch The git branch N78-APA assumes for this app — usually main. Should match the branch you tag and release from.
- Credential vault Encrypted locker for store logins, git tokens, and other secrets. Copy-only access — values never shown on screen after save.
- Clipboard security for secrets Vault copy buttons paste without displaying values. The clipboard clears automatically after a few seconds.
Microsoft Store listing
- Package identity name Permanent MSIX / APPX package identity (reverse-DNS). Must match AppxManifest.xml and cannot change after first Store release.
- Store listing title and descriptions Product display name (max 200), short description (max 256), and full description (max 10000) — validated before save.
- Privacy policy requirements Microsoft Store apps that collect data need a public privacy policy URL. Prepare the link before submission.
- Age ratings and content declarations Complete content questionnaire answers during prep so Partner Center certification matches your app.
- Edit and validate before save Every field and image stays easy to change. Checks run before save so Partner Center entry uses spec-compliant answers.
- Plain-language field guides Each input explains what it is, what it is used for, size and format requirements, and where the answer is stored on disk.
Images & screenshots
- Store logo set PNG logo variants for Microsoft Store — 300×300, 150×150, 71×71, and 50×50 pixels.
- PC screenshots Screenshot set for desktop Store listing — spec-sized images validated before export.
- Promotional images Optional promotional artwork for Store discovery — prepare when your listing strategy calls for it.
Partner Center
- When to open Partner Center Open Partner Center for live signup and submission after N78-APA checklists are complete — not before.
- Testing tracks overview Optional reference guides for testing tracks and staged release after listing prep is complete.
- Does N78-APA upload to the store? Not in V1. The mission is validated preparation — metadata, images, export packages, and readiness checklists.
Plans & roadmap
- V1 free Microsoft Store scope V1 — the current free desktop preview — covers Microsoft Store (Windows PC) publishing preparation.
- V2 multi-store upgrade V2 will be a paid upgrade adding Google Play and Apple App Store workflows alongside Microsoft.
- Where your data lives Portable project folder next to your source code — under .apa metadata. No cloud account required for the desktop preview.