Microsoft should prioritize official cross-platform In-App Purchases (IAP) for .NET MAUI (Android + iOS)

[ThomasMunch]

Short version: .NET MAUI needs an official, first-party IAP component for both Google Play and the App Store. This is core to developers and to Microsoft’s ecosystem because it directly affects whether we can monetize our apps—and whether MAUI remains a compelling choice for new projects.

Why this is critical

Without first-party support we must maintain two divergent implementations (Play Billing vs. StoreKit/StoreKit 2) → higher complexity, more defects, larger QA surface, and higher maintenance costs.

Community packages are helpful but often incomplete or lagging behind store updates and policy changes.

The absence of a unified IAP story weakens MAUI’s competitiveness versus other cross-platform frameworks.

What is needed from Microsoft

One stable API surface for purchases/restores/acknowledgements; product types (consumable, non-consumable, subscriptions); transaction events (pending/cancel/refund); price-change flows; and subscription management.

First-party documentation and end-to-end samples, including server-side receipt validation for both stores.

A clear roadmap and support policy (Play Billing/StoreKit versions; .NET 9/10; LTS), so teams can plan releases and business commitments with confidence.

I strongly urge MS to prioritize this capability. An official IAP component would materially improve MAUI’s time-to-revenue and reduce churn to competing technologies.

it will make a tangible difference for MAUI developers and for Microsoft’s platform.

Best regards,
Thomas Munch
indie .NET MAUI developer for DeepInkCode

[rokmeglic71]

@ThomasMunch you are not alone on this. Related previous discussion where you have partial solution, also a no no from CommunityTookit developers. Why? You can read more about this here.