Sparkle VS msix

* i use appimagelauncher[1] to integrate with my menus etc but sometimes it works and sometimes it doesn't? i haven't really figured out the rhyme or reason

[0] https://sparkle-project.org/

I'm glad I'm not the only one that thinks checking every 5 mins is a little bit excessive!

Seeing as it's macOS only is there even any reason to roll your own update mechanism when you can use the Sparkle framework [1]?

[1]: https://sparkle-project.org/

The bucket contains dmg files and an appcast.xml that allows for updates. I'm using the auto_updater package, which in turn uses the popular Sparkle library.

Our build process is automated using fastlane. That handles building and testing the app as well as signing, notarizing and uploading to Amazon S3. We distribute via a link on our website -- Callisto. Updates are handled using Sparkle. We have a custom built appcast generator as part of our website that reads the S3 bucket and builds the feed that Sparkle uses.

Something like Sparkle but for Node.

I am trying to create a windows installer according to this link https://pub.dev/packages/msix

The bucket contains MSIX installers and an App Installer file that points to the MSIX of the most recent build. The MSIX files are built with the msix package, and the App Installer is generated using a custom Dart script I wrote.

So you're asking whether a Windows app written with Flutter has the same problem with dependencies as a .NET app? Why don't you simply test it? Take any Flutter app you like, compile it, create an installer and ask your support department whether that would be easier for them to distribute?

The easiest way to generate an MSIX installer is by using a Flutter package called msix. This is a command line tool that helps in creating an MSIX installer from the Flutter Windows build files.

I came across this lib for Flutter Windows build that helps you to create MSIX Installer for direct install as well as for Windows Store. But what is lacking, is the way to build the .pfx certificate that is kind of equal to the .keystore file in Android apps for signing Release build.