Deploy & App Stores
Push, In-App Purchases and Deep Links for AI-Built Native Apps
Push notifications, in-app purchases and deep links are the three features that turn a wrapped AI-built web app into a real product, and each needs work in four places: your web code, the native shell, Apple and Google's consoles, and your backend. Plan them together, because they share infrastructure such as user IDs, domains and server endpoints.
How do push notifications work for a web app turned native?
Native push uses Apple Push Notification service (APNs) on iOS and Firebase Cloud Messaging (FCM) on Android; the app registers for a device token and your backend sends messages to it. Web push from your original web app does not carry over automatically.
Many teams use FCM for both platforms, since it can deliver to iOS through APNs once you upload an APNs key in Firebase.
- Create an APNs key in your Apple Developer account and enable the Push Notifications capability in Xcode
- Create a Firebase project, add Android and iOS apps, include the config files
- Add a push plugin (Capacitor Push Notifications, Expo Notifications or your wrapper's built-in support)
- Request permission at a meaningful moment, including Android 13+ runtime permission
- Send the device token to your backend and associate it with the user
- Send notifications from your backend or a serverless function
What are the common push pitfalls?
Asking for permission on first launch, forgetting to refresh tokens and sending from the client are the usual mistakes. Never put FCM server credentials in the app; sending must happen server-side.
Handle notification taps by routing to the right screen, which connects push to your deep link logic.
When do you need in-app purchases?
If you sell digital goods or subscriptions consumed in the app, Apple's guideline 3.1.1 generally requires In-App Purchase, and Google Play generally requires Google Play Billing. Physical goods and real-world services can use Stripe or similar.
Rules for linking to external purchases have changed in some regions and keep evolving, so check the current guidelines for your markets instead of assuming your web checkout is allowed.
- Digital subscriptions, credits, premium features: store billing
- Physical products, bookings, real-world services: your own payment provider
- B2B apps where accounts are bought outside the app: specific rules apply, review them carefully
How do you implement in-app purchases in a hybrid app?
Use a purchase plugin or a subscription service SDK that abstracts StoreKit and Google Play Billing, and validate receipts on your server. The server is the source of truth for entitlements, so the same user sees premium features on web, iOS and Android.
Set up products in App Store Connect and Play Console, test with sandbox and license testers, and handle restores, refunds and expirations through server notifications.
How do deep links work on iOS and Android?
Deep links open specific content in your app from emails, web pages or notifications. On iOS you use Universal Links with an apple-app-site-association file on your domain; on Android you use App Links verified through an assetlinks.json file.
Both files are served from the .well-known path of your domain, which is easy with most hosting platforms used by AI builders, as long as you use a custom domain you control.
- Serve apple-app-site-association and assetlinks.json on your domain
- Add the Associated Domains capability in Xcode and intent filters on Android
- Handle incoming URLs with Capacitor's App plugin, Expo Linking or your wrapper
- Map URLs to routes in your app's router
- Use the same deep links for OAuth callbacks and notification taps
How do the three features fit together?
They share user identity and routing: a push notification carries a deep link, the deep link opens a screen, and that screen checks the user's purchase entitlement. Design one routing table and one user model for all three.
AI coding agents such as Claude Code, Codex, Cursor or Windsurf can implement each piece well when you give them this architecture explicitly; app builders like Lovable or Bolt.new usually need the native parts added after export.
Where can you get help?
These features touch accounts, certificates and policies on both platforms, which is where projects stall. WebViewGold includes many native features such as push for wrapped web apps, and neooutput's AI Code Engineers implement custom setups with Capacitor or Expo.
Frequently asked questions
Can I use web push instead of native push in my app?
Inside a native app you should use native push via APNs and FCM. Web push applies to browsers and installed PWAs, not to apps distributed through the stores.
Can I keep using Stripe in my iOS app?
For physical goods and real-world services, yes. For digital goods and subscriptions used in the app, Apple generally requires In-App Purchase, with region-specific exceptions that change over time.
Do deep links need a custom domain?
For Universal Links and App Links you must serve verification files on a domain you control, so a custom domain is strongly recommended.
Can one backend handle purchases from web, iOS and Android?
Yes. Store all entitlements server-side and validate store receipts there, so users get the same access on every platform.
