# Signs your dating app needs a rebuild

Published 2026-10-16. Updated 2026-10-16. https://www.datingapi.io/insights/signs-dating-app-needs-rebuild

**In short:** A dating app needs a rebuild when its technology stops it doing the basics: shipping updates every few weeks, passing store review, keeping crashes under Google Play's thresholds, adding verification, taking payments reliably and meeting new law. One sign can be fixed. Several at once, plus dependence on one or two engineers, usually means the platform itself is the problem.

A dating app needs a rebuild when its technology, not its team or its marketing, is what stops it improving. The signs are practical and measurable: updates take months instead of weeks, store submissions keep getting rejected, crash rates creep towards Google Play's thresholds [6], ratings slide, verification or new safety features can't be added, payments fail in ways nobody can explain, only one or two people understand the system, and a new law or store deadline arrives that the app cannot meet [3][8].

Any one of these can usually be fixed in place. Several together usually mean the platform is the problem. Even the largest operators reach this point: in March 2026 Bumble's chief executive told investors "we cannot deliver the innovations we are creating on our legacy tech stack" [1].

## Why rebuilds happen even at scale

Bumble is the clearest public example. On its fourth quarter 2025 call it said it was "rearchitecting the entire Bumble experience from start to finish", describing "a fully new platform that will transform how we build and ship product" [1]. Its chief financial officer warned of "some duplication of costs for a portion of 2026" while old and new systems ran side by side [1]. By its second quarter 2026 results, the company said it was "completing our platform migration" [2].

Match Group took a different route to the same place, moving its smaller brands onto shared systems. In August 2026 it said these brands were "benefitting from shared Match Group capabilities, including Trust and Safety", and that "the major platform migrations" were complete [10].

The lesson for smaller operators is not that every app needs rebuilding. It is that the decision is a normal part of running a dating app, and the cost of delaying it compounds.

## The eight signs, and how to measure each

### 1. Releases have slowed to a crawl

Measure the time between store releases over the past year, and the time from a finished change to it reaching members. If a small change, such as a new profile prompt, takes a month or more to ship because every release risks breaking something, the codebase is slowing you down. Look at how many releases were hotfixes for problems the previous release caused.

### 2. Store submissions keep getting rejected

Apple reviewed 7,771,599 app submissions in 2024 and rejected 1,931,400 of them [7]. By our calculation that is about 24.9% of submissions (1,931,400 divided by 7,771,599) [7]. The biggest single reason was performance, cited in 1,235,471 rejections [7]. Track your own rejection rate per submission and the reasons. Repeated rejections for crashes, broken flows or missing account deletion point to an app that is hard to keep compliant.

### 3. Platform deadlines keep arriving faster than you can meet them

Both stores raise their minimum technical requirements every year:

- **Google Play target API level:** from 31 August 2026, new apps and updates must target Android 16 (API level 36), with extensions available to 1 November 2026 [3]. Existing apps that target Android 14 or lower are only available to new members on devices running that version or older [3].
- **Google Play Billing Library:** by 31 August 2026, all new apps and updates must use version 8 or later [4].
- **Apple SDK:** since 28 April 2026, apps uploaded to App Store Connect must be built with Xcode 26 using an iOS 26 SDK [5].
- **Apple age ratings:** developers had to answer updated age rating questions by 31 January 2026 to avoid interruptions when submitting updates [5].

If each of these turns into a multi-month project, or depends on an outdated library nobody maintains, that is a sign.

### 4. Crash rates are rising

Google publishes the line. Its overall bad behaviour threshold is a 1.09% "user-perceived crash rate" and a 0.47% "user-perceived ANR rate" (app not responding), with a per-phone-model threshold of 8% for each [6]. Above those, "Play may reduce the visibility of your title" and may show a warning on the store listing [6]. Check Android vitals and your iOS crash reporting monthly, and watch the trend, not just the level.

### 5. Ratings are falling

Compare your rating over the past 90 days with your lifetime rating, on both stores. Then read the one and two star reviews and tag them. If most complaints are about bugs, freezes, lost messages or login failures rather than the dating pool or pricing, the problem is technical.

### 6. You can't add verification or safety features

Photo verification, [ID verification](/glossary/id-verification), [age assurance](/glossary/age-assurance), better reporting and moderation tooling are now expected. Measure how long the last safety feature took from decision to launch. If adding one means touching code nobody understands, or the moderation team works across several disconnected tools, the platform is holding back trust and safety.

### 7. Payments are unreliable

Measure renewal success, refunds, chargebacks and support tickets about missing purchases. Check how often a member's entitlement in your database disagrees with Apple's or Google's records. Apple retries failed renewals for 60 days and offers a billing grace period so members keep access while a payment issue is resolved [9]. If your backend can't handle those states correctly, paying members lose access or keep it for free.

### 8. Everything depends on one or two people

Count how many people can deploy the backend, restore a database, or release to the stores without help. If the answer is one, or if a contractor who left holds the knowledge, you have key-person risk. Ask what happens to releases if that person is unavailable for a month.

### And a ninth: a new law you can't meet

In the UK, Ofcom's illegal content codes of practice came into force on 17 March 2025, and its protection of children codes on 25 July 2025 [8]. Similar age rules are spreading, as our [age verification guide](/insights/age-verification-dating-apps) sets out. Measure it simply: list each obligation that applies to you and ask whether the app can meet it today. If the honest answer is "not without a rebuild", that settles it. See also our [Online Safety Act checklist](/insights/online-safety-act-dating-apps).

## Self-assessment table

Score each line 0, 1 or 2.

| Sign | 0: healthy | 1: watch | 2: act |
| --- | --- | --- | --- |
| Release cadence | Every two to four weeks | Every one to two months | Quarterly or slower |
| Store rejections | Rare, quickly fixed | Recurring for the same reasons | Blocking releases |
| Store deadlines | Met with time to spare | Met late or with extensions | Missed or at risk |
| Crash rate | Well under Google's thresholds | Close to a threshold | Over a threshold |
| Ratings trend | Stable or rising | Slipping | Falling, with bug complaints |
| Safety features | Added in weeks | Added in months | Can't be added |
| Payments | Entitlements match store records | Occasional mismatches | Regular lost or free access |
| Key people | Three or more can release | Two can release | One person or an ex-contractor |
| New law | Can meet it now | Can meet it with work | Can't meet it |

Source: Dating API framework, using Google Play thresholds [6] and store deadlines [3][4][5].

How to read it: a total of 0 to 4 points to fixes in place; 5 to 9 calls for a plan, starting with the lines that scored 2; 10 or more, or a 2 on store deadlines or new law, usually means a rebuild or a move to a different platform. These bands are our judgement, not an industry standard.

## Rebuild, replatform or patch

A rebuild does not have to mean starting from nothing. The options are:

- **Patch:** fix the worst lines in the table and buy a year. Right when only one or two signs score 2.
- **Rebuild in house:** right if you have a strong technical team and the time. Budget for running old and new systems in parallel, as Bumble did [1].
- **Move to a managed platform:** right if the app's value is the brand and the members, not the code. Our [build vs buy guide](/insights/build-vs-buy-dating-app) sets out the trade-offs, and [app build](/app-build) explains how we rebuild an app on an operator's own store listings.

Whichever route you take, the move itself is a separate risk. Our guide to [migrating a dating app without losing members](/insights/migrate-dating-app-without-losing-members) covers keeping the listing, data and subscriptions intact.

## What it means for dating app operators

- **Measure before deciding.** Release cadence, rejection reasons, crash rates and payment mismatches are all available today. Score the table honestly.
- **Store deadlines are fixed dates.** The 31 August 2026 Google Play requirements and Apple's April 2026 SDK rule show the pace [3][4][5]. An app that struggles with each one will keep struggling.
- **Safety is now a technical capability.** If verification and moderation can't be added quickly, regulation will force the issue.
- **Key-person risk is a business risk.** It affects valuations and sale processes, not just engineering.
- **Plan for parallel running.** A rebuild costs more for a period before it costs less.

## Questions

**How do I know if my dating app needs a rebuild or just fixes?**

Count the signs. A single problem, such as a crash spike, can usually be fixed in place. When releases are slow, store deadlines keep slipping, verification can't be added and only one or two people understand the system, the cost of patching usually exceeds the cost of rebuilding.

**What is the Google Play target API level deadline in 2026?**

From 31 August 2026, new apps and app updates must target Android 16 (API level 36), with extensions available to 1 November 2026. Existing apps must target Android 15 or higher to stay available to new members on newer Android devices [3].

**What crash rate does Google Play treat as bad?**

Google's overall bad behaviour threshold is a 1.09% crash rate as perceived by people using the app, and 8% on any single phone model. Above it, Play may reduce the app's visibility and show a warning on the listing [6].

**Did Bumble rebuild its app?**

Yes. In March 2026 Bumble's chief executive said it could not deliver its plans on its legacy tech stack and was building a fully new platform [1]. In August 2026 she said Bumble was completing its platform migration [2].

## Sources

1. Bumble Inc Q4 2025 earnings call transcript, ROIC.ai, 2026-03-11. https://www.roic.ai/quote/BMBL/transcripts/2025-year/4-quarter
2. Bumble Inc. second quarter 2026 results, Bumble Inc (SEC filing), 2026-08-05. https://www.sec.gov/Archives/edgar/data/0001830043/000183004326000099/bmbl-ex991prxq22026.htm
3. Meet Google Play's target API level requirement, Android Developers, 2026-10-16. https://developer.android.com/google/play/requirements/target-sdk
4. Play Billing Library version deprecation FAQ, Android Developers, 2026-10-16. https://developer.android.com/google/play/billing/deprecation-faq
5. Upcoming requirements, Apple Developer, 2026-10-16. https://developer.apple.com/news/upcoming-requirements/
6. Android vitals, Android Developers, 2026-10-16. https://developer.android.com/google/play/vitals
7. 2024 App Store Transparency Report, Apple, 2025-05-30. https://www.apple.com/legal/more-resources/docs/2024-App-Store-Transparency-Report.pdf
8. Important dates for Online Safety Act compliance, Ofcom, 2026-10-16. https://www.ofcom.org.uk/online-safety/illegal-and-harmful-content/important-dates-for-online-safety-compliance
9. Auto-renewable subscriptions, Apple Developer, 2026-10-16. https://developer.apple.com/app-store/subscriptions/
10. Match Group Q2 2026 shareholder letter, Match Group (SEC filing), 2026-08-04. https://www.sec.gov/Archives/edgar/data/0000891103/000089110326000128/mtch8-k20260804ex992.htm