feat: add documentation for plugins

[lucasfernog]

No description provided.

[netlify]

✅ Deploy Preview for tauri-docs-starlight ready!

Name	Link
🔨 Latest commit	0980f5a
🔍 Latest deploy log	https://app.netlify.com/sites/tauri-docs-starlight/deploys/64f9f37563d2e80008bbd8f1
😎 Deploy Preview	https://deploy-preview-1412--tauri-docs-starlight.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
Lighthouse	1 paths audited Performance: 100 (no change from production) Accessibility: 100 (no change from production) Best Practices: 100 (no change from production) SEO: 92 (no change from production) PWA: - View the detailed breakdown and full score reports

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[lorenzolewis]

Just going to capture a few notes to self here:

• Some sections such as "lifecycle events" might belong in the references section instead, lets us elaborate on them without making the guide too heavy
• Do android and iOS pages need to be separate guides? This is something we're talking about overall for the docs and how much we separate mobile concepts from desktop concepts. I'm in favour of keeping them as close as possible to minimise API and UX divergence between desktop and mobile.
• Refer directly as Swift and Kotlin, not iOS and Android

---

Will do a more thorough review ASAP. Would love to use this as a solid reference to do a community/PR push to "develop and show us your Tauri 2.0 plugins" if/when we feel this is all stable enough.

[lorenzolewis]

Did some formatting on this one, need more input from dev to move further.

[lorenzolewis]

I'll try to jump in on this one tomorrow and get the conflicts and structure cleaned up based on the updates and inputs from today. Thanks @lucasfernog 💜

[lorenzolewis]

@lucasfernog I can see this chunk of documentation going in 1 of 2 ways:

1. Keep it specific to mobile plugin development like we have now
2. Use this as a baseline for building out a more extensive IPC guide for Swift and Kotlin/Java

The chunk on Commands I can see really fitting into a Commands/IPC guide and then we split that up a bit by language instead of platform. But I don't know how you want to position this feature and if it's in the spirit of a full-fledged IPC/binding for Swift and Kotlin/Java.

The JS IPC is really all handled by Tauri via invoke so it's a lot more accessible to end users. Whereas now (from what I understand) the Swift and Kotlin/Java IPC is really positioned more towards library/plugin authors. So it's your call on who you feel would be the proper target audience (specifically for the Commands sections). I can shift it into whichever direction based on that (right now it's in the direction of point 1 above).

[lucasfernog]

The Kotlin/Swift IPC is only exposed for plugins, so IMO it doesn't make sense to move them out of the plugin documentation. Most application users will just want to leverage existing plugins instead of implementing custom logic for Android and iOS, and those who can do so, will need to write a plugin and go through all that documentation (and hopefully open source it to give back to the community ❤️ ).

[lorenzolewis]

@lucasfernog wrapped up all the formatting and stuff for this one. I have one to-do that I'm going to take care for the CLI reference in the guide, but could you take a look at the other comments?

I think this one is good to go as soon as those are resolved 🥳

[lorenzolewis]

TODO for @lorenzolewis

[lorenzolewis]

Finally! (Siri, play Finally by CeCe Peniston)

Thanks @lucasfernog and @simonhyll