Can I send mobile push notifications from a Base44 backend function?

Yes. When you wrap your Base44 app with AppNative, the native shell registers each user's iOS (APNs) and Android (FCM) device token and links it to their Base44 user email. Any Base44 backend function or workflow can then send a push notification with a single POST request to AppNative's push API, including deep links, badge counts, custom sounds and images.

How do I add Apple StoreKit in-app purchases to a Base44 app?

Enable In-App Purchases in AppNative. AppNative creates your subscription or consumable products directly in App Store Connect and Google Play, compiles a native StoreKit 2 and Play Billing paywall into your app, and syncs active entitlements back to your Base44 User or Subscription entity while letting you keep Stripe for web users.

AppNative › Blog › Base44 Native Capabilities

How to add push notifications, widgets, and in-app purchases to a Base44 mobile app

Updated October 2026

Short answer: Wrapping your Base44 web app with AppNative gives your Base44 code native iOS and Android superpowers without rewriting your frontend: trigger APNs/FCM push notifications from any Base44 backend function by user email, sell subscriptions via StoreKit 2 and Google Play Billing while keeping Stripe on the web, and compile AI-designed WidgetKit home-screen widgets and Dynamic Island Live Activities fed by your Base44 entities.

1. Sending Push Notifications from a Base44 Backend Function

Once Push Notifications are toggled on in AppNative, the native iOS and Android wrapper automatically prompts the user for permission and associates their device token with their signed-in Base44 email. From any Base44 backend function (base44/functions/yourFunction/entry.ts), you can send a push notification with one HTTP call — or let AppNative's AI helper inject the trigger into your existing Base44 function automatically.

See the full guide: Push Notifications for Base44 Apps.

2. Selling Subscriptions with StoreKit 2 & Google Play Billing

Apple Review Guideline 3.1.1 prohibits using Stripe checkout inside an iOS app for digital subscriptions or credits. With AppNative's In-App Purchases for Base44 Apps:

Keep your existing Stripe checkout for desktop and mobile web browsers.
Inside the native iOS and Android app, AppNative intercepts your upgrade route (e.g. /upgrade or /pricing) or responds to window.AppNative.iap calls and opens a native StoreKit 2 / Google Play Billing paywall.
AppNative automatically creates the subscription products in App Store Connect and syncs purchase and renewal webhooks back to your Base44 entities so your app checks one unified status.

3. WidgetKit Home-Screen Widgets & iOS Live Activities

Unlike basic WebView wrappers, AppNative compiles real SwiftUI app extensions into your iOS binary. In the Widget Studio and Live Activity Studio, you describe the widget you want in plain English, connect it to a Base44 JSON endpoint, and AppNative compiles the native WidgetKit and ActivityKit targets into your TestFlight build.

4. Face ID, Camera, Contacts, Apple Wallet & Offline Mode

Every other device capability is available as a toggle in the AppNative wizard and exposed to your Base44 frontend via window.AppNative: biometric Face ID / Touch ID lock, Apple Wallet & Google Wallet passes, native share sheet, haptic feedback, and offline caching.

Add native features to my Base44 app