Nothing matches that. Try a shorter word, or browse the topics.
Your users already keep their music, health records, contacts and calendars on the device. These libraries put each store behind one cross-platform API, handle the permission dance, and — where it helps — expose it to an AI agent.
Query, browse and play the device music library
Query tracks, browse by genre, decade or playlist, and play music from the device library. Mobile-only: there is no equivalent of iOS MediaPlayer or Android MediaStore elsewhere.
Apple HealthKit and Android Health Connect behind one API
Unified access to HealthKit and Health Connect — read, write and observe twelve metrics including steps, heart rate, blood pressure and sleep.
Store version checks, store and review deep links, and the in-app review prompt
Ask the App Store, Google Play, the Microsoft Store or Flatpak/Snap whether a newer version of the running app is published, open its store or review page, and request the native in-app review prompt - all from one IAppStore.
The store-shared age range for Texas SB 2420 and other app store age laws
Read the user's age range as the app store shares it - Apple Declared Age Range and Google Play Age Signals - from one IAgeSignals, with nullable age checks that never mistake "unknown" for "no".
StoreKit 2 and Google Play Billing 9 behind one API, with the backend included
Sell consumables, non-consumables and subscriptions through the App Store and Google Play from one IInAppPurchaseManager. The server package verifies purchases and turns App Store Server Notifications and Google Play RTDN into one stream of purchase events.
Device contacts with full CRUD and LINQ queries
Access device contacts with full CRUD, a fluent async query builder with native translation, and Shiny's AccessState permission model. Runs in any Shiny host, with or without .NET MAUI.
Device calendars and events with CRUD and LINQ queries
Full CRUD on device calendars and events on iOS, Mac Catalyst, macOS, Android and Windows, with a LINQ query that pushes the calendar id and date window down to the native fetch.
Block and identify incoming calls on iOS and Android from a list your app owns
Your app keeps a list of numbers to block or label, and the phone applies it to every incoming call even when the app is not running — through a Call Directory extension on iOS (built during dotnet build, no Xcode project) and the call screening role on Android.
