Creating a universal package is useful, but this package requires the user to be on a mac development environment to use it. This doesn't seem like it should be necessary. Requiring a mac build environment creates friction for using this tool.
Suggestion: Make this package work regardless of the development platform. I don't know how feasible this is as I am not sure what technical limitation is currently making it platform-specific.
For context, we have a game on Steam which we release Windows / Linux / Mac versions for. We have been releasing a darwin-x64 package, but we have users reporting slowness on modern macs. If we switch the mac packages to arm64, then it would be a compatibility break for users on older x64 Mac machines, so we were considering using universal packages, but the requirement of using a mac build platform is making it more difficult than it ought to be to make a universal package, and we will probably have to go with a different, less elegant solution.
Creating a universal package is useful, but this package requires the user to be on a mac development environment to use it. This doesn't seem like it should be necessary. Requiring a mac build environment creates friction for using this tool.
Suggestion: Make this package work regardless of the development platform. I don't know how feasible this is as I am not sure what technical limitation is currently making it platform-specific.
For context, we have a game on Steam which we release Windows / Linux / Mac versions for. We have been releasing a darwin-x64 package, but we have users reporting slowness on modern macs. If we switch the mac packages to arm64, then it would be a compatibility break for users on older x64 Mac machines, so we were considering using universal packages, but the requirement of using a mac build platform is making it more difficult than it ought to be to make a universal package, and we will probably have to go with a different, less elegant solution.