[ronyfadel]

Hi enatik, I’m 100% your target audience, so I have some feedback.

I use Sparkle + Github Releases to update my apps (you can test the update process at https://fadel.io), and I’ve been looking to automate the process as it’s becoming a hassle. Your landing page’s value proposition isn’t clear to me. Yes updating is a hassle. The leading framework on macOS is arguably Sparkle. How does it do the job better than Sparkle?

I want my process to be fire and forget, as in: notarize the app, generate the appcast.xml, upload the binaries and update the remote appcast.xml after being asked for the changelog, and ideally also test that the update works correctly.

I’m not sure how Pakky solves that, if at all.

FYI I’m currently looking to automate the whole process with a script.

[emayljames]

Just an aside for enatik, in the UK pakkly, if spelled wrong as done innocently here, can end up as a very racist slur for Pakistanis. I'd seriously consider changing the name.

[austinjp]

Ouch. Agreed, that's the first thing that came to my mind, and it's an unfortunate to see it happen here. Definitely consider a name change!

[grandpoobah]

Wait, do you mean Paki?

It's two whole letters away.

-1 for name change.

[enatik]

I haven’t used Sparkle myself so I may be a bit off, but as far as I can see Sparkle requires you to constantly update an xml file so it knows what to update. Pakkly allows you to specify a glob to search for in the releases area. So you can simply target myapp_mac_*.zip and your users will automatically be updated when they next start the app. Notarization is a process I’m planning to integrate via a CLI, if possible.

Also, it’s cross platform, if you ever decide to branch out :)

[sgottit]

I had a similar problem – which I opened sourced here; http://replay.software/bump. Bump basically automates all of the Sparkle signing and appcast creation using GitHub Actions, and then pushes the binary & changelog to AWS automatically with Terraform.