Shopify Mobile
October 23, 2026Outgrowing Tapcart or Another App Builder? How to Switch Without Losing Your Listing
The biggest fear about leaving a Shopify app builder is starting over: a new listing, zero reviews, and asking every customer to download a different app. That doesn't have to happen. Here is what transfers, what breaks, and the order to do it in.
Short answer
Your listing can come with you. Ship the new app under the same bundle ID and package name, signed so Google Play accepts it as an update, and customers get it as an ordinary update with your reviews intact.
Your app's code cannot. Builders render your app from their platform, so the app itself is rebuilt.
Check whose developer account the app is in first. If it is the builder's, plan a transfer to yours, and do the preparation Apple requires before you request it.
Signs you have outgrown your builder
- The bill keeps climbing. You moved up a tier to unlock one feature, or your revenue share now costs more than a flat plan would.
- You are waiting on someone else's roadmap. The feature your brand needs, such as a drop mechanic, a loyalty flow, or a product configurator, is “on the roadmap” with no date.
- Your app looks like everyone else's. Templates and blocks get you live fast, and they also make apps look alike.
- You need data you can't get. Event-level analytics or a warehouse feed is locked behind a higher tier, or not offered at all.
If the only problem is price, another builder may be the answer, and our builder price comparison lays out what each one charges. If the problem is control, switching builders just moves it.
What transfers with the listing
The store listing is separate from the code that runs it. Apple ties a listing to its bundle ID, which “can't be changed once a build has been uploaded.” Google ties it to the package name, and only accepts updates signed with the app's key. Upload a new build with the same identifier and the right signing, and the stores treat it as the next version of your app.
If the app currently sits in the builder's developer account, both stores let you move it to yours:
- Apple: a transferred app “retains its reviews and ratings, and users continue to receive updates” (Apple's app transfer overview).
- Google Play: users, download statistics, ratings and reviews, and store listing information transfer. Google's support team reviews each request and replies within 2 business days (Google's transfer guide).
What breaks, and how to plan for it
The app is rebuilt, so everything the builder wired up for you has to be wired up again. If the app also moves between developer accounts, Apple lists a few things that don't carry over cleanly:
- Apple Pay: “the merchant ID isn't transferred along with the app.” You create a new one in your account.
- Push certificates: existing APNs certificates keep working until they expire. After that you need your own certificate or APNs key, and your push provider has to be updated.
- Keychain sharing: works only until the app is updated. After the update, signed-in customers have to log in once more.
- TestFlight: builds and testers must be removed, and the test information fields cleared, before Apple will start the transfer.
- Sign in with Apple: each user needs a transfer identifier generated so their account carries over, and grouped apps must be ungrouped first.
- Google Play test tracks and integrations: test groups have to be recreated, and Firebase and Google Analytics links updated.
None of these is a reason to stay. They are a reason to plan the cutover rather than improvise it.
The switching checklist
- Confirm whose developer accounts the app lives in. Open App Store Connect and the Google Play Console. If the app is listed under the builder's team rather than yours, plan a transfer, but do the preparation below first: Apple requires some of it before a transfer can start.
- Write down the bundle ID and package name. The new app must ship with exactly these identifiers. That is what makes it an update to the existing app rather than a separate listing that starts at zero reviews.
- Secure Android signing. Google Play only accepts an update signed by the app's key. If the app uses Play App Signing, Google holds that key and you need access to the upload key or a reset of it. If it doesn't, get the original signing key from the builder. Without it, matching the package name is not enough to ship an update.
- Prepare sign-in before the transfer. If the app uses Sign in with Apple, Apple requires apps in a Sign in with Apple group to be ungrouped before transfer, and each user needs a transfer identifier generated so they keep their account. Coordinate this with the builder before you request the transfer.
- Export what the builder will let you take. Push audience and segments, app-only discount codes, analytics history, and any content you created in the builder's editor. Ask for this before you give notice.
- Inventory every integration. Reviews, loyalty, subscriptions, search, wishlists, and analytics. Each one has to be reconnected in the new app, and some vendors charge separately for their mobile SDK.
- Plan the push notification cutover. Push tokens are issued to your app on each device and registered with whatever push provider the builder used. Plan for the new build to register devices with your new provider as customers update.
- Move deep links to your own domain. Universal links and Android app links are verified against files hosted on your domain. Make sure they point at the new app before launch so links in emails and ads still open the app.
- Overlap, don't gap. Keep the builder subscription active until the new version is approved and rolled out. Cancelling first can leave customers on an app that has stopped working.
Another builder, or custom?
Moving to another builder is the faster, cheaper switch, and it is the right one if price is the only problem. You still rebuild the app, but inside a new editor, and you still don't own the code at the end.
A custom app is a real project. We quote 4 to 6 weeks for a typical Shopify app and 6 to 8 with deeper integrations like custom checkout or headless storefronts. Shopify provides the building blocks: the Storefront API for catalog and cart, and Checkout Kit for checkout. At the end you own the code, and the monthly cost is a retainer for changes rather than a per-tier subscription.
Frequently asked questions
Can I switch builders without losing my App Store reviews?
Yes, if the new app ships under the same bundle ID and package name, and the Android build is signed so Google Play accepts it as an update. Customers get it as an update, and the listing keeps its reviews and ratings. If the app is in the builder's developer account, prepare and transfer it to yours first.
What is a good Tapcart alternative?
Another builder if you mainly want a lower bill. Appbrew, Plobal, Apptile, and Vajro all list plans on the Shopify App Store. A custom app if you want features and code ownership a builder can't give you. Compare three-year totals, not monthly prices.
What breaks when you move a Shopify app?
The app itself is rebuilt, and push, deep links, analytics, and app-only discounts are reconnected. Across developer accounts, the Apple Pay merchant ID doesn't transfer, keychain sharing ends at the next update, and APNs certificates must be replaced when they expire.
How long does it take to switch?
A few weeks to move to another builder, most of it configuration and store review. We quote 4 to 6 weeks for a custom rebuild, 6 to 8 with deeper integrations. A Google Play transfer adds review time on top.
Weighing a move off a builder? We build custom iOS and Android apps for Shopify brands, and you own the codebase at the end.