Question you want answered

After just creating my first Tauri App, what I need to know and how so I can build my Tauri App.

Where did you look for an answer?

More specific, I've been testing the Tauri 2.0 beta on my personal Web App to try port it to Mobile and Desk native apps (.dmg .exe .apk, etc).
And, following the https://v2.tauri.app/start/create-project/ in the quick starts worked like a charm :rust: :tauri: 🇹🇩
Then the thing that interest me the most about the migration from an existing project to Tauri is how to build my app into the executables or installable bundles (.dmg, .exe, .apk, etc). So, the guide in the next steps suggested me this links which the Learn How to Build your Tauri app(img 1) was the most important for me.

But the page that it leads is empty currently. (img 2)
https://v2.tauri.app/develop/

So I wanna fill this guide on how build my App

Page URL

https://v2.tauri.app/start/create-project/#next-steps

Additional context

I don't know if the current redirect that this link makes goes to the section that represents a Build guide. By build I mean Build and Deploy the executables .exe, .dmg or ios, etc, for the targeted platform that the developer needs to ship the app. So there are a few questions that need to be answered there.

Are you willing to work on this yourself?

• I want to work on this myself

Checklist

• Prerequisites: e.g. to build your app you need to have a working app on development e.g. (getting started create a project)
• CLI Commands to build App (include reference to the CLI reference docs)
• Building Tauri app for Windows
• Building Tauri app for Mac
• Building Tauri app for Linux
• Building Tauri app for Android
• Building Tauri app for iOS
• Other edge cases?
• Have a Next Steps section well defined

WIP: Next Steps Ex:

• Next Steps: Platform-specific configuration?
• Next Steps: DevOps integrations so the build is made automatically (link with custom docs with snippets and guide on how to CI/CD the builds with GitHub Actions.
• Next Steps: Common deployment cenários e.g. host the exe on a website. Or for example with Android. It's very common to publish your APK at Google Play. So the docs should at least mention that with the generated APK the developer has everything he needs to continue with the publishing process on PlayStore (maybe even provide some official Google link on how to publish apps in PlayStore, although this could easily break due to changes on google side.)