基于Angular+Cordova的应用：OS X平台选Cordova还是Electron更合适？

Great question! Since you already have an Angular/Cordova app targeting Android and iOS, and you're exploring desktop support for OS X—especially with file system storage needs—let’s break down how these two tools stack up.

Core Fit for OS X Platform #

First, the big picture:

• Electron is built specifically for desktop apps (OS X, Windows, Linux) using web tech. It’s designed to blend web UIs with native OS features seamlessly. For OS X, this means out-of-the-box support for platform-specific behaviors that users expect.
• Cordova is primarily a mobile-focused tool that happens to support OS X as a secondary platform. It wraps your web app in a minimal native shell, but desktop isn’t its core use case.

Cordova: Pros & Cons for OS X #

Pros #

• Zero to minimal code changes: Your existing Cordova codebase (including plugins like cordova-plugin-file for file system access) will work almost as-is on OS X. No need to rewrite core logic for desktop.
• Smaller app footprint: Cordova’s OS X shell uses the system’s built-in WebKit instead of bundling a full Chromium instance, so your final app size will be significantly smaller than an Electron equivalent.
• Familiar toolchain: You already know how to build, package, and deploy Cordova apps—no need to learn a new workflow from scratch.

Cons #

• Limited native OS X integration: Cordova’s support for OS X-specific features is sparse. Customizing the menu bar, dock icon interactions, Touch Bar support, or system notifications requires third-party plugins (many of which are poorly maintained or outdated).
• Performance gaps: Since desktop isn’t Cordova’s focus, the shell isn’t optimized for OS X’s performance nuances. You might notice slower load times or jank compared to an Electron app.
• Weak community support: Most Cordova resources, tutorials, and bug fixes are focused on mobile platforms. If you hit a desktop-specific issue, finding help will be harder.
• Stagnant platform updates: Cordova’s OS X support lags behind Electron’s. New OS X features (like Ventura’s window management tools) might take months or longer to be supported, if at all.

Electron: Pros & Cons for OS X #

Pros #

• Native OS X experience out of the box: Electron gives you full access to OS X’s system APIs. You can build custom menu bars, dock context menus, integrate with the Touch Bar, use system notifications, and implement proper window management—all with official, well-documented APIs.
• Flexible file system access: Instead of relying on Cordova plugins, you can use Node.js’s built-in fs module directly in your Angular app. This makes file operations faster, more flexible, and easier to debug.
• Vibrant desktop-focused community: Electron is the de facto standard for web-based desktop apps (think VS Code, Slack, Discord). If you run into issues, there’s a huge community of developers ready to help, plus tons of tutorials and third-party libraries.
• Robust packaging & distribution: Tools like electron-builder make it trivial to package your app into a signed DMG, set up auto-updates, and comply with OS X’s security requirements (like notarization).
• Smooth Angular integration: Since Electron uses Chromium, your Angular app will run exactly as it does in a modern browser. You can even reuse your existing Angular services and components with minimal tweaks.

Cons #

• Larger app size: Electron bundles a full Chromium instance and Node.js runtime with every app. Expect your final DMG to be 50MB+ (compared to 10-20MB for a Cordova app).
• Higher memory usage: Chromium’s overhead means Electron apps use more RAM than Cordova’s lighter shell. For users with limited resources, this might be a concern.
• Plugin migration work: If your app relies heavily on Cordova plugins (like camera, geolocation), you’ll need to replace them with Electron-native alternatives (e.g., desktopCapturer for camera access). This adds upfront development time.
• Frequent version updates: Electron updates regularly to keep up with Chromium’s security patches and feature updates. While this is good for security, it means you’ll need to periodically update your Electron version to avoid compatibility issues.

Final Recommendation #

• Choose Cordova if your top priorities are fast time-to-market and minimal development effort. It’s perfect if you just need a basic desktop port of your existing mobile app without fancy OS X-specific features.
• Choose Electron if you want a polished, native-feeling OS X app with strong long-term maintainability. It’s the better choice if you plan to invest in desktop-specific features and want to deliver an experience that feels natural to OS X users.

Since you need robust file system access, Electron’s direct Node.js support will make that part of your app more reliable and easier to work with compared to Cordova’s plugin-based approach.

内容的提问来源于stack exchange，提问作者Cyril Lacroix