1. Do what browsers can't: Open files.
2. Do stuff offline.
3. Combine with other tech.
4. Do computationally intense stuff.
5. Distribution/Exposure.

• Node.js + Chrome
•  ⤷ Customized libuv + libchromium

• Node.js + Chrome
•  ⤷ Customized libuv + libchromium

1. HTML
2. CSS
3. JavaScript
4.  ⤷ Frontend + Server Side

• Native menus and notifications
• Automatic Updates (Evergreen)
• Crash Reporting
• Windows Installers
• App Store Distribution (MAS Builds)
• Devtron

1. Community & release pace.
   
   
2. Github is vested in it.
3. Quick wins.
4. Windows, macOS, & Linux.
5. Single-browser focus: Just Chrome.
6. Code reusability.

1. Partial promises: feature relevance.
2. Windows, macOS, & Linux.
3. Browser ➞ Desktop mental shift.
4. Advanced use can be difficult & not as well documented.
5. Footprint
6. Don't use it only as daemon.
7. Don't use it only as task menu.

1. Most things translate well (UI).
2. macOS has 3 menus, Windows has 2
3. Autoupdates do not work on Linux.
4. Jumplists are Windows only.
5. macOs Touch Bar

• .exe, .msi, .dmg, .bin, NSIS (Installer)
• electron-packager
• electron-builder

• Github/Web
• Squirrel Autoupdates
• Store-based Updates
• Linux Updates

1. Open app, paid service.
2. Custom Licensing Solution

Commercial apps need code signing.

• Expect to buy TWO certificates.
• Expect to pay $110/yr (after tax) for an Apple Developer License.
• Expect to pay $60-250/yr for basic Windows Code Signing Certificate.
• Expect to pay $100-500/yr for Extended Validation Windows Code Signing Certificate (Authenticode).
• Expect painful CI/CD with EV certificates.
• Avoid StartSSL, Buy Digicert, Use massive MS discount.

• macOS Autoupdates won't work without code-signing.
• Apple App store distribution requires MAS build: No autoupdates, no crash reporting.
• Windows Store: AppX only (Windows 10+)
• No code protection by default (except asar).

• Recognize Autoupdates are hard.
• Recognize crash reporting is easy, but reading them is hard.
• System logging doesn't exist (yet). Don't worry.
• Avoid native node modules.
• Use event-oriented architecture, avoid socket.io.
• Don't support Linux commercially unless that's you're market.
• Test early and often on each operating system.
• Treat development like web development, but remember it's the desktop.

• Static Desktop Web Server
• Secure Realtime Collaboration
• Dead Simple Deployments
• author.io
• fenixwebserver.com
• 40K+ Users, ~1100 Github Stars

• Deploying from Github: Chassis

• Deploy from Codepen: NGNX Example
• Building the Badge

• Choosing the right UI framework.
• Autoupdates for multiple editions (Core, PRO, Team).*
• Proprietary Code Protection: Plugin Architecture.*
• Licensing.*

http://edgeATX.github.io/slides

Corey Butler — @goldglovecb

Fenix coming soon to Author.io