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?

首先查看 repository 中现有的 native binding 示例，然后比较 issue 中提到的 payment 和 printer SDK 示例的 Android 与 iOS binding 是如何组织的。一个有价值的结果是记录每个 provider 是否应拥有独立的 binding 项目，或者按类别划分的项目是否合适，并包括有关依赖隔离和维护的指导。

由索引模型根据 Issue 内容生成。