Replace Shopify apps with code: what a 60-line section saves

A striking share of what Shopify stores pay for every month is rented code that a short Liquid section would own outright. One industry audit of 27 stores found 23 of them paying subscriptions for features a sixty-line section could deliver server-side, free, forever. Replacing an app with code means rebuilding its one useful feature as a native part of the theme, and for a surprising number of apps that rebuild is an afternoon, not a project.

The money is the visible half of the case. The quieter half is weight, each installed app ships scripts costing 40 to 200 milliseconds of mobile load time, the tax measured across real stores in our app bloat audit, and a store carrying ten apps pays that tax on every visit before a single product renders.

Which apps are actually replaceable

The replaceable ones share a shape, a single display feature, no external data, no ongoing service behind it. The app renders something on the page, the something never changes shape, and the subscription continues monthly regardless.

The countdown deserves its own caveat, the replacement section counts toward a real date someone set on purpose, and when no real deadline exists the section stays unused, which is the honest version of urgency and the only one that survives a buyer refreshing the page.

What stays app-shaped, anything with a real service underneath. Reviews apps collect and verify, email platforms send, subscription engines bill, search apps index, those subscriptions buy ongoing work, and rebuilding them makes no sense. The line is service versus display, and most stores have three to six display apps billing monthly on the wrong side of it.

The math over a year

An illustrative stack, not a client’s. Four display apps at an average of $19 each run $76 a month, $912 a year, climbing as the apps upsell tiers. The one-time replacement build for all four sits in the low hundreds each at typical dev rates, paid once. By month eight the code has paid for itself, and every month after is margin, plus the permanent speed refund of removing four script bundles from every page load.

Why the sections end up better, not just cheaper

The rented widget arrives styled by someone else, close to the brand, never quite of it. A native section uses the theme’s own type, spacing, and color tokens because it lives inside them, nothing to override, no CSS fights at midnight. Editing moves into the normal theme editor, the same place the rest of the store gets managed, and the marketing team stops filing tickets to change a testimonial. And when an app company sunsets a product or triples a price, the store with native sections reads the email with complete indifference.

There is a durability point buried here too. Uninstalled apps famously leave code behind, the leftover-snippet problem from our store speed guide, while a native section leaves nothing to leave, it either serves or gets deleted cleanly. Ownership is tidier in both directions.

How to run the replacement, in order

Audit first, the full app list with each one’s monthly cost and its actual job written next to it, most founders find at least one app nobody remembers installing. Sort into service versus display. Replace the display apps worst-first, worst meaning heaviest script or highest fee, and rebuild each as a section with editable blocks so the team keeps self-service, the build pattern from custom Shopify sections. Test the section live, then uninstall the app, then sweep the theme for its leftovers, that order specifically, so the store never shows a gap. The whole discipline is the technical debt cleanup most stores never schedule, done once, owned after.

Speed the replacement earns should get measured, before and after, same tool, same page, because the number makes the case for the next replacement, and the one after. The measuring method sits in our speed checklist.

One build detail decides whether the team loves or resents the replacement. The section gets built with editable blocks and settings, every quote, every question, every image swappable from the normal theme editor, because a section only a developer can touch has traded a subscription for a bottleneck. Online Store 2.0 made this the default pattern, blocks the marketing team rearranges themselves, and a replacement built that way is not a downgrade in convenience wearing a discount, it is the same self-service the app sold, minus the rent and minus the scripts. Ask for that explicitly when commissioning the work, editable blocks, no hardcoded content, the theme editor as the only tool anyone needs afterward.

FAQ

Which Shopify apps can code replace?

Display apps, testimonials, FAQs, comparison tables, sticky bars, countdowns, before/after sliders. Anything rendering a fixed feature with no service underneath.

Which apps should stay?

The ones doing ongoing work, reviews collection, email sending, subscriptions billing, search indexing. A subscription buying real service is fair rent.

What does replacing an app cost?

A display app’s section typically runs a few hundred dollars built properly, once. The app charges monthly forever, the crossover usually lands inside a year.

Will replacing apps break the store?

Not in the right order. Build the section, test it live, uninstall the app, sweep its leftovers. The store never shows a gap between steps.

Do sections load faster than apps?

Yes, structurally. Sections render server-side inside the theme, apps inject external scripts, the 40-to-200-millisecond kind, on every page load.

Want your app list sorted into keep-versus-replace, with the yearly math run? Send me the store and I will mark up the stack. Free look, no obligation, usually a reply within the hour.