Best Practices for Structuring Multiple Native SDK Bindings in .NET MAUI

When integrating multiple third-party native SDKs into a .NET MAUI application, such as payment providers (Square, Stripe) and hardware integrations (Epson, Star Micronics printers), what is the best approach for organizing bindings?

Would it be better to create separate Android/iOS binding projects for each SDK?
For example:

- Square.Android.Binding and Square.iOS.Binding
- Stripe.Android.Binding and Stripe.iOS.Binding
- Epson.Android.Binding and Epson.iOS.Binding
- StarMicronics.Android.Binding and StarMicronics.iOS.Binding

Alternatively, would it be more efficient to consolidate bindings within a single project per category (e.g., one Payments Binding for Square & Stripe and one Printers Binding for Epson & Star Micronics), while maintaining distinct implementations for each provider?

What are the best practices for structuring these bindings to ensure scalability, maintainability, and minimal dependency conflicts in a .NET MAUI application?

Review the repository's existing native binding samples first, then compare how Android and iOS bindings are organized for the payment and printer SDK examples named in the issue. A useful outcome would document whether each provider should have separate binding projects or whether category-level projects are appropriate, including guidance on dependency isolation and maintenance.

索引モデルが issue の本文から書いたものです。