How to Shut Down a Mobile App Properly

Shutting down a mobile app has a few extra layers compared to a web product. You have to deal with two app stores, in-app purchase policies, users who might not see your shutdown announcement for months, and data that lives on devices you don't control.

Step 1: Plan Your Timeline Around App Store Policies

Both Apple and Google have policies around app shutdowns that affect refunds and timing.

Apple (App Store):

• Apple may issue refunds to users for in-app purchases if they determine the app was shut down before a reasonable usage period
• Notify Apple support if you're doing a planned shutdown — they can help coordinate
• Remove the app from the store at least 30 days before backend shutdown to prevent new downloads

Google (Play Store):

• Similar policies apply for in-app purchases
• Use the "Unpublish" option (not delete) so existing users can still access it temporarily
• Consider leaving it published but showing an in-app shutdown notice

Step 2: Show an In-App Notice Before Shutdown

The most effective way to reach your users is inside the app itself. Before you do anything else:

1. Release an app update with a prominent shutdown notice
2. Include the exact shutdown date
3. Include instructions for data export if available
4. Send a push notification to all opted-in users

Don't rely solely on email. Mobile users often ignore emails but open push notifications.

Step 3: Handle In-App Purchases

Refunds for in-app purchases are split between you and the app store, which complicates things:

• You only control your 70% (or 85% for small developers) of the purchase price
• Apple and Google collect their 30% cut and have their own refund policies
• You may need to coordinate with their developer relations teams for large-scale refunds

For subscriptions: cancel all active auto-renewals before your backend shutdown date. Most subscription management libraries (RevenueCat, etc.) let you cancel in bulk.

For consumables and one-time purchases: issue refunds via your own backend for any unused credits or locked content. For content that was consumed, contact Apple/Google about their policies for your specific case.

Step 4: Data Deletion and Privacy Compliance

Mobile apps often collect data that's subject to GDPR, CCPA, and platform-specific privacy policies. Before shutdown:

• Delete all user data from your servers (or document your data retention policy)
• If users have local data on their devices, you can't delete it — but you can document that backend data will be deleted
• Send a final privacy notice explaining what's happening to stored data

For apps with user-generated content: Give users a way to export or download their data before you shut down the backend.

Step 5: Coordinate with Review Sites and App Catalogs

Your app is listed on various review sites (Product Hunt, GetApp, Capterra, AppFollow). These sites don't automatically know you've shut down. Consider:

• Notifying major review sites directly
• Updating your own Product Hunt post with a shutdown announcement
• Updating any public documentation that references the app

This prevents confusion when people find your app through these channels months after shutdown.

Step 6: Keep Your App Website Up

Your app's website (landing page, support page) should be redirected to a shutdown notice. Users who Google your app name should land on a clear explanation, not a 404.

This page should include:

• What the app did
• Why it's shutting down
• When the app stopped working
• What happened to user data
• Any alternatives you'd recommend

The Users Who Install it After Shutdown

If you leave the app in the store (even as "no longer maintained"), new users may download it expecting it to work. Be clear in the store listing description that the app is shut down, or remove it entirely.

An app that shows nothing but a "service has ended" screen is worse than no app at all for a new user who didn't know about the shutdown.

Final Checklist

Before you turn off the lights:

• App update with shutdown notice released
• Push notifications sent
• Subscriptions cancelled
• Refunds issued
• Data deletion scheduled and documented
• App removed or marked as discontinued in stores
• Website redirected to shutdown page
• Support email monitored for 90 days post-shutdown

Mobile shutdowns have more surface area than web shutdowns. The checklist helps.