How do I add an app to the Store?

[DcS79c]

I want to learn a programming language. If I wanted to add an app to the Microsoft Store, what is the procedure?
I know that Apple charges developers $99/year to be a developer. Does Microsoft charge as well? Assuming that I'm able to add the app to the Store, what is the procedure?

 

[ChatGPT]

Hi DcS79c — great question. Short answer: yes, you can publish apps to the Microsoft Store. Below I’ll give a compact step‑by‑step of the full procedure (account, packaging, submission, certification, post‑publish), plus the current cost/details and language recommendations so you can pick where to start.

• Costs / developer account
• Individual developer accounts: Microsoft now offers free registration for individual developers in most markets (no $19 onboarding fee).
• Company (organization) accounts: there’s a one‑time registration fee (typically around USD $99, varies by country) and additional verification requirements.
• Which language / app type to learn (brief guidance)
• If you want native Windows desktop apps: learn C# with .NET (WPF, WinForms, or WinApp SDK / WinUI).
• If you want cross‑platform or web tech: JavaScript/TypeScript with Electron or a Progressive Web App (PWA).
• If you need high performance/native code: C++ (Win32).
  Choose based on your goals (desktop utilities → C#/.NET; cross‑platform UI → Electron/.NET MAUI; web integration → PWA). If you tell me your goals I’ll recommend a concrete starter path.
• High‑level submission procedure (what you’ll actually do)
• Create a Microsoft account (MSA) and register as a developer in Partner Center (choose Individual or Company). Partner Center is where you manage apps, listings and submissions.
• Reserve an app name in Partner Center so nobody else can claim it (you can reserve before the app is finished; reserve holds last for the period Microsoft allows).
• Build and package your app. Microsoft recommends packaging as MSIX (benefits: Microsoft offers free signing/hosting for Store‑distributed MSIX packages); EXE/MSI submissions are also allowed but MSIX is preferred. Use the MSIX Packaging Tool or your build pipeline to create the package.
• Prepare Store listing assets: description, category, screenshots for each device family, store logo, privacy policy URL (required if you collect personal data), age rating questionnaire, pricing/availability settings, etc.
• Upload package(s) and metadata in Partner Center, choose pricing/markets, and submit for certification. Partner Center validates fields before submission.
• Certification & publishing: Microsoft runs technical, security and content checks. Certification for MSIX/PWA submissions typically completes in up to a few business days; once it passes it can appear in the Store quickly. You’ll get status updates in Partner Center.
• Packaging notes and signing
• MSIX is recommended (automatic updates, better Windows integration, Microsoft provides free signing/CDN hosting for Store packages). If you keep an EXE/MSI you must follow the Store rules for installers (no bundling unrelated software, offline installer, etc..
• Monetization & revenue share (important if you plan to sell)
• You can publish free apps or paid apps, and use in‑app purchases/subscriptions. If you use Microsoft’s commerce platform Microsoft takes a share (Microsoft has published competitive splits historically; for apps Microsoft has used a ~15% cut and for games ~12% when Microsoft handles commerce). Microsoft also supports the option for certain non‑game apps to use your own commerce system (letting you keep 100% of revenue in those cases). Check the current Partner Center/Store commerce docs for exact percentages and rules that apply to your app type.
• Certification pitfalls to avoid (common rejections)
• Missing or low‑quality screenshots or logos, missing privacy policy when you collect personal data, installers that change after submission, bundled adware/unwanted software, or use of restricted APIs/capabilities. Follow the certification checklist in Partner Center to reduce rejection risk.
• Timeline & post‑publish
• Name reservation: you can reserve before publishing.
• Certification: typically up to a few business days for MSIX/PWA (varies).
• After publishing you can push updates, use flighting (staged rollouts), view analytics/crash reports in Partner Center, and manage in‑app purchases from the dashboard.
• Quick checklist to get started right now
• Decide app type and pick a language/framework.
• Sign up in Partner Center (Individual if you’re publishing as a personal developer).
• Follow a tutorial to build a simple app (e.g., a “Hello world” desktop app), then package it as MSIX and create a draft submission in Partner Center to see required fields.
  If you want, I can:
• Recommend the best language/framework given the app you want to build.
• Walk you through creating an MSIX package from a small C# app (I can give exact commands and steps).
• Walk through Partner Center screens and the minimum metadata you need to fill out.

Which type of app do you want to build (desktop utility, game, productivity tool, web app/PWA, etc., and what’s your current programming experience? That will let me give a tailored step‑by‑step to get your first Store app published.

 

[DcS79c]

Thank you for the quick reply.

I don't know if I would ever submit an app to the Windows store but maybe I would. I wondered about Linux as well & boy is it complicated to submit an app to the Linux repo!

I've tried Pascal & "pre" VB.NET & VB.NET. I want a language that is cross-platform. There are only 2 ways that I'm aware of to create a cross-platform app - .NET & Java. .NET doesn't have to deal with Java baggage. I read online that originally only .NET Core was cross-platform but now .NET is also cross-platform. I also found out that the Community edition of VS or is it VS Code is free? I can afford free! So, I need to decide which language to choose - C# or VB.NET.

 

[ChatGPT]

You’re welcome — good thinking to compare the languages before committing. Short answer: for a cross‑platform future, pick C#. Here’s why, plus practical next steps and tooling.
Why C# is the safer choice for cross‑platform

• .NET today is a modern, cross‑platform platform (Windows/macOS/Linux, plus mobile and WebAssembly options) and first‑class tooling and frameworks are focused on C#. Visual Studio’s .NET pages list C# and Visual Basic as .NET languages, but the cross‑platform frameworks and new features are C#‑centric.
• .NET MAUI (the official Microsoft framework for single‑codebase native apps on Android/iOS/macOS/Windows) currently does not provide VB project templates — MAUI development is C#‑centric. If you want native cross‑platform GUI apps, C# is the practical choice.
• Visual Basic (VB.NET) is still supported by Microsoft (docs, language reference, and you can build console/.NET class libraries), so it’s fine for learning and for maintaining Windows‑centric apps — but it gets fewer cross‑platform UI options and less new‑feature attention than C#. Use VB if you prefer its syntax and you plan Windows‑only / legacy work.

Tooling — free options

• Visual Studio Community (full IDE) is free for individual developers and other qualifying scenarios; it’s the easiest way on Windows to build .NET apps and has built‑in designers and project templates. Check the Visual Studio licensing pages for details on permitted uses.
• Visual Studio Code is a lightweight, free, cross‑platform editor (Windows/macOS/Linux) with excellent C# extensions (and works well if you want to develop on Linux or macOS).

Practical recommendation (if you want cross‑platform)

1. Learn C# and the modern .NET SDK (dotnet CLI). Start with console apps so you learn the language and tooling. (Common commands: dotnet new console, dotnet run.
2. After basics: pick a target:
   • Web/cross‑platform UI: learn Blazor (web + WebAssembly) or ASP.NET Core for server/web APIs.
   • Native cross‑platform GUI: learn .NET MAUI (C#).
   • Desktop Windows only: WinForms/WPF (these are Windows‑only and can be done in C# or VB).
3. Use Visual Studio Community on Windows for GUI projects and Visual Studio Code if you want lightweight, cross‑OS editing.

Pros/cons summary

• C#: pros = best ecosystem for cross‑platform, lots of learning resources, frameworks (MAUI, Blazor, ASP.NET), wide community and job market. Cons = new syntax to learn only if you’re used to VB.
• VB.NET: pros = familiar if you’ve used classic VB/VB.NET; still supported for many .NET scenarios. Cons = fewer cross‑platform UI options, less momentum for new cross‑platform features.

If you want, I can:

• Give a short 30‑day learning plan for C# (daily steps + small projects).
• Walk you through installing the .NET SDK and creating your first C# console app (exact commands and IDE setup).
• Show how to create a simple cross‑platform UI prototype in Blazor or .NET MAUI (depending on whether you prefer web or native UI).

Which would you prefer to try first — a console tutorial in C# (fast way to learn language basics), or a tiny GUI prototype (Blazor or MAUI)? I’ll give step‑by‑step instructions for whichever you pick.