Mac App Store Deployment Guide is Out-of-Date and Incorrect

[HEIC-to-JPEG-Dev]

The deploymnet guide for the app store, https://docs.avaloniaui.net/docs/deployment/macOS is old and out of date.

I would love to help update it - but as I've not yet found any conclusive AvaloniaUI guide for completing this task, I cannot.

From my perspective, I want to use AvaloniaUI, but without that final piece of the puzzle; and I'm sure a lot of people would take-up AvaloniaUI if there was a wizard; it becomes another dead-end product. Don't get me wrong, I love AvaloniaUI, but the deployment part (to Windows as well, although MS made that easy) is essential and not (as I keep getting told) "nothing to do with Avalonia"

It's like trying to buy a BMW and they won't tell me how to pay for it. Nothing to do with them, ask the bank, who then point you at a list of API's.

[timunie]

It's like trying to buy a BMW and they won't tell me how to pay for it. Nothing to do with them, ask the bank, who then point you at a list of API's.

That comparison doesn't really fly here, as Avalonia is for free. If you get the BMW for free, you also can't claim anything. Still feedback is appreciated. If you are a paying customer, reach out to the team and we can help you sorting things out.

[MikeCodesDotNET]

macOS and iOS packaging and deployment have always been challenging, even when building Xamarin.Mac and Xamarin.iOS projects.

The documentation, however, is (for the most part) correct; it's just not easy to grasp. I've successfully used it to package and notarize the FamilyShow demo, which is only 1 step away from app store deployment.

That said, we need to improve the documentation around this. Longer term, we have a plan to improve the whole app packaging experience, but that'll become part of our "Pro" tooling, which will have a very modest fee attached.

[HEIC-to-JPEG-Dev]

macOS and iOS packaging and deployment have always been challenging, even when building Xamarin.Mac and Xamarin.iOS projects.

The documentation, however, is (for the most part) correct; it's just not easy to grasp. I've successfully used it to package and notarize the FamilyShow demo, which is only 1 step away from app store deployment.

That said, we need to improve the documentation around this. Longer term, we have a plan to improve the whole app packaging experience, but that'll become part of our "Pro" tooling, which will have a very modest fee attached.

Do you have a timeline ? - I'm not shy in paying for it, but I'm also in the position of "What technology stack to use for MacOS" - the only solid option at the moment in xCode/Swift/SwiftUI

[MikeCodesDotNET]

It's a H2 priority, but I can't share any timeline other than that as we don't discuss timelines for products publicly.