Distribución mediante tiendas de aplicaciones

Distributing your Electron app through official app stores like the Microsoft Store or Mac App Store offers several benefits.

These include increased discoverability, enhanced user trust, and simplified updates for your users.

Before submitting to any app store, your Electron application needs to meet common requirements. These often include:

• Code Signing: Ensures your app's authenticity and integrity.
• Sandboxing: Limits your app's access to system resources for security.
• Specific Package Formats: Stores require particular installer formats, like MSIX for Windows or a signed pkg for macOS.

The Microsoft Store is a digital distribution platform for Windows apps. Submitting your Electron app here can reach a vast audience of Windows users.

The key requirement for the Microsoft Store is packaging your application into an MSIX format.

MSIX is a Windows app package format that provides a reliable way to deploy apps. Tools like electron-builder can automate this process for your Electron app.

You'll configure electron-builder in your package.json to specify MSIX details, like publisher identity.

Here's a simplified example:

Once your MSIX package is ready, you'll use the Microsoft Partner Center to submit your app:

• Register: Enroll in the Windows Developer Program.
• Create Submission: Start a new app submission in Partner Center.
• Upload Package: Upload your generated MSIX file.
• Add Details: Provide app name, description, screenshots, pricing, age ratings, and availability.
• Publish: Submit for review and eventual publication.

The Mac App Store (MAS) is Apple's platform for macOS apps. It has stricter security and sandboxing requirements compared to the Microsoft Store.

Distributing via MAS gives your app credibility and reach within the Apple ecosystem.

Sandboxing is mandatory for Mac App Store apps. It restricts what your app can do, limiting access to user files, network resources, and system functions unless explicitly granted.

This is a crucial security measure that prevents malicious apps from harming user data or the system.

Entitlements are specific permissions that your sandboxed app needs to perform certain operations. They are declared in a special file (e.g., .entitlements) and embedded in your app.

Common entitlements include network access, access to user's Downloads folder, or camera/microphone access. You must only request what your app truly needs.

Example of an entitlement file:

Submitting to the Mac App Store involves using Apple's App Store Connect and Transporter tool:

• Apple Developer Program: Enroll and ensure your app is notarized (covered in a previous lesson).
• App Store Connect: Create a new app record, providing metadata, pricing, and screenshots.
• Upload Package: Use Xcode or the Transporter app to upload your signed and sandboxed pkg file.
• Review: Apple reviews your app for compliance with their guidelines.
• Release: Once approved, you can release your app.

It's vital to understand the key requirements for distributing your Electron app through official app stores.

In this lesson, we explored how to distribute your Electron applications via the Microsoft Store and Mac App Store.

We covered the importance of specific packaging formats (MSIX for Windows, signed pkg for macOS), mandatory security features like sandboxing, and the role of entitlements for macOS apps.

Understanding these distinct processes is key to successfully reaching users through official channels.