On the analytics/ASO side, the LetsMetrix, AppJubilee and Marmeto write-ups are a reasonable starting map of replacements — worth skimming before committing to any of them.
But the more useful question is the one bkspace pointed at. A drop-in replacement won’t buy back the trust Mantle had, and it’s worth being precise about why Mantle wound down: Shopify shipped native App Pricing in May, and Mantle’s billing became redundant. Services end Aug 14, billing Sep 30. The risk that kills an app usually isn’t a competitor — it’s the platform absorbing the feature. Almost nobody checks for it before they build.
I run that check on every idea now, against merchant forum threads cross-referenced with the live App Store and Shopify’s changelog. Since a few of you are re-deciding what to build, here’s a worked example — including the part where it went against me.
Six weeks ago my check cleared purchase-order receiving as a clean, native-safe gap. Stocky sunsets Aug 31 with its APIs, Shopify’s native POs don’t cover the receiving workflow — receiver doc, retail price at receipt, non-barcoded label print — and there was no PO API or any public signal of one.
On July 17 Shopify published the Physical Inventory feature preview: bins, counts and purchase orders as GraphQL Admin primitives. My “no signal” was wrong inside a month.
The nuance is the useful part. The preview is unstable-only, gated per store, and purchase orders are read-only — no create, no receive. So the merchant gap on Aug 31 is real and still unserved. But the verdict changes: this went from a durable gap to a timing play with a closing window. A thin receiving bridge for the Stocky crunch, charged for now — fine. A deep PO platform built on it — that’s the Mantle shape again.
Sharing it because it’s the honest version, and because it’s the same pattern that just hit Mantle: the product didn’t lose, the platform absorbed it. If anyone here wants that check run against whatever you’re weighing, name the idea in-thread and I’ll give you my read for free.