Match Factory · Peak
Product Analysis · 2026
What happens when failure resets more than the level?
Executive summary
Store reviews analyzed
5,575
Levels logged, no purchases
55
Penalties from one loss
5
One loss costs more than one life.
On my non-paying Match Factory account, a continue cost nearly my entire coin balance, while the same loss could reset up to four progression systems on top of the life. Hypothesis: stacked loss penalties may turn difficulty into perceived paywall pressure for stuck players.
Context
Match Factory (Peak) leads the Match 3D subgenre and retains better than its closest rival, which makes the strain this case finds later worth taking seriously.
It took 56% of the subgenre's revenue in H1 2025, against 22% for Triple Match 3D (AppMagic). The core loop taps cluttered 3D objects to a shelf at the bottom of the screen; three identical objects clear, and a level is lost when the shelf fills or the timer runs out. Coins buy a continue, and emptying the shelf costs 100 coins on the fail screen.
By level 53, nine timed systems (streaks, races, team goals, an item hunt, a pass and a collection) are visible on the home screen at once. Early 2024 iOS data put its D1 and D3 retention at 45% and 32%, against 27% and 19% for Triple Match 3D (Naavik). This case asks where that strength runs out.
Three sources: my own play logs on a fresh, non-paying account (levels 1 to 55), screenshots, and a classified dataset of 5,575 App Store and Google Play reviews across both games.
How to read this case
Three kinds of claim sit side by side here: what I logged directly from my own play (labeled own play logs), public data I did not generate (store reviews, AppMagic, Naavik, and similar sources, cited inline), and what I am proposing or assuming (hypothesis, proposal, and any figure marked illustrative). None of it is Dream Games' or Peak's internal data.
Question
Match Factory's tension is deliberate and largely works: it leads the subgenre in revenue and in early retention. The question is where that tension stops working, and whether the cost of a single loss compounding across several systems at once is part of why some players describe hitting a paywall.
Observations
One loss can trigger up to five penalties at once. To compare two economies without comparing their currencies, I use continue coverage: coin balance divided by continue price, the number of losses a player can buy back before having to pay or quit.
Life · 1 of 5
Win streak · Chef's Tool resets, up to 5 tiers of starting boosters
No-fail event · Treasure Cave run broken (7 levels without failing, for 1,000 coins)
Score multiplier · Helmet Rush resets, ×1 to ×10
Items collected · Item Hunt items shown as lost on the fail screen
The event penalties apply only while those events are running. Every retry after the first loss starts without streak boosters, which makes the next loss more likely.
| What a loss costs | Match Factory (levels 1 to 55) | Royal Match (Case 1, levels 1 to 60) |
|---|---|---|
| Life | 1 of 5 (unlimited-life timer often active) | 1 of 5 (unlimited-life timer often active) |
| Win streak | Chef's Tool resets: up to 5 tiers of starting boosters | First-try streak events reset |
| No-fail event | Treasure Cave: 7 levels without failing, for 1,000 coins | Not observed |
| Score multiplier | Helmet Rush: multiplier x1 to x10 resets | Not observed |
| Items collected in the level | Item Hunt items shown as lost on the fail screen | Not observed |
| Continue coverage | 1 to 2.2 (100 to 220 coins / 100) | about 7.3 (6,600 coins / 900) |
What a loss costs
Life
Match Factory (levels 1 to 55)
1 of 5 (unlimited-life timer often active)
Royal Match (Case 1, levels 1 to 60)
1 of 5 (unlimited-life timer often active)
What a loss costs
Win streak
Match Factory (levels 1 to 55)
Chef's Tool resets: up to 5 tiers of starting boosters
Royal Match (Case 1, levels 1 to 60)
First-try streak events reset
What a loss costs
No-fail event
Match Factory (levels 1 to 55)
Treasure Cave: 7 levels without failing, for 1,000 coins
Royal Match (Case 1, levels 1 to 60)
Not observed
What a loss costs
Score multiplier
Match Factory (levels 1 to 55)
Helmet Rush: multiplier x1 to x10 resets
Royal Match (Case 1, levels 1 to 60)
Not observed
What a loss costs
Items collected in the level
Match Factory (levels 1 to 55)
Item Hunt items shown as lost on the fail screen
Royal Match (Case 1, levels 1 to 60)
Not observed
What a loss costs
Continue coverage
Match Factory (levels 1 to 55)
1 to 2.2 (100 to 220 coins / 100)
Royal Match (Case 1, levels 1 to 60)
about 7.3 (6,600 coins / 900)
Scarcity & loss pressure · findings 1 to 3
Lives and boosters were repeatedly replenished, while coins stayed close to the continue price.
Over 55 levels with zero purchases, my balance went from 100 coins at install to 220, staying flat at about 100 for most of levels 15 to 35. Event rewards leaned toward lives, boosters and cards; one event payout gave two card packs, 15 minutes of unlimited lives, a timed rocket, a rocket and a fan. The continue costs 100 coins, so for this account one continue meant spending everything, the opposite of the Royal Match account in Case 1, where coins piled up and lives were the abundant resource.
The players who fail are also the players least likely to earn the largest coin rewards.
The biggest coin prize I saw, 1,000 coins from Treasure Cave, requires seven levels in a row without a single loss. Helmet Rush and Chef's Tool follow the same rule. A player who is struggling earns fewer coins exactly when they need them for continues, while a player on a streak earns more. Scarcity lands hardest on the players closest to quitting.
The fail screen concentrates multiple losses into the same decision moment.
When my shelf filled around level 30, with 2:22 still on the timer, the fail screen read "You will lose" above the 30 Item Hunt items collected in that level, then offered to empty the shelf for 100 coins, exactly my balance, with a Starter Discount (99.99 TL, "95% off": 200 coins, four boosters, an hour of unlimited lives and two boosters) embedded below. My first offer appeared at level 23, the first level marked Hard and the moment my Chef's Tool streak was full at 5/5. One observation, but the first offer arrived when a loss was most expensive.
Player signals · findings 4 and 5
Among the reviews analysed, Match Factory draws difficulty and paywall complaints at roughly twice the rate of its closest rival.
Among 1 to 2 star App Store reviews, Match Factory mentions difficulty, pay-to-win and coin scarcity two to three times as often as Triple Match 3D, while its rival draws more complaints about ads and bugs.
Share of 1-2 star App Store reviews mentioning each theme
Difficulty
Pay-to-win
Misleading ads
Coin scarcity
Ad complaints
Bugs and performance
Own review dataset, App Store only: Match Factory 1,821 and Triple Match 3D 1,649 reviews, rule-based classification.
Match Factory reviewers who say they quit or are about to
Difficulty complaints also rise with progress, peaking between levels 1,000 and 3,000 (19% of reviews naming a level in the 1 to 200 band mention difficulty, versus 72% in the 1,001 to 3,000 band). Each band holds only 12 to 69 reviews, so this is a direction, not a measurement.
Reviews are weak at detecting the early-session friction that is easiest to fix.
My own early sessions had clear friction: at level 49 (Super Hard) I needed three attempts because objects in similar colours blended together and taps sometimes picked the wrong object when I played fast. Yet complaints about visual clarity, mis-taps, shelf filling and lost streaks together appear in under 3% of Match Factory's negative reviews. The likely reason is who writes reviews: more than half of the reviews that name a level are past level 200. The one early-churn signal reviews do show is ad mismatch: 19.6% of negative reviews say the game is not what its ads showed, often adding they deleted it within the hour.
Key observation
Early friction has to be measured in play data, not reviews. The players most likely to churn in the first few sessions are the ones least likely to have left a review about why.
Opportunity
Reduce the stacked penalty, not the difficulty.
The opportunity is not to make levels easier or coins cheaper across the whole economy, but to stop one loss from turning into several at the moment a player is already stuck. Match Factory's tension largely works; the cost appears later, when hard levels and stacked penalties meet a balance that cannot cover a continue. That is when reviewers start describing a paywall and quit statements cluster.
Hypothesis
For players starting a third attempt on the same level, giving back what the first loss took will raise the share who play again within 24 hours and improve D7 retention, without reducing revenue per user beyond a set guardrail.
Proposal
At the start of the third attempt on the same level, the player gets back what the first loss took: the Chef's Tool boosters for that attempt, and on a win, the Helmet Rush multiplier and Treasure Cave run as they stood before the first loss.
How the shield plays out
Attempt 3 starts
Level 49, Super Hard
If attempt 3 is lost
Out of space!
If attempt 3 is won
Level complete!
Full specification
| Element | Design |
|---|---|
| Who sees it | All players past level 20 (after Chef's Tool unlocks), paying or not |
| Trigger | Start of the third attempt on the same level |
| On that attempt | Starts with the Chef's Tool boosters the player had before the first loss |
| If it is won | Helmet Rush multiplier and Treasure Cave run restored to their pre-loss state |
| If it is lost | Only the life is lost; the shield carries to the next attempt |
| What it never gives | Coins, a continue, or more than the player had before the first loss |
| Limit | Once per level, at most three levels per day |
Element
Who sees it
Design
All players past level 20 (after Chef's Tool unlocks), paying or not
Element
Trigger
Design
Start of the third attempt on the same level
Element
On that attempt
Design
Starts with the Chef's Tool boosters the player had before the first loss
Element
If it is won
Design
Helmet Rush multiplier and Treasure Cave run restored to their pre-loss state
Element
If it is lost
Design
Only the life is lost; the shield carries to the next attempt
Element
What it never gives
Design
Coins, a continue, or more than the player had before the first loss
Element
Limit
Design
Once per level, at most three levels per day
The shield restores progress rather than protecting it going forward, since Chef's Tool, Helmet Rush and Treasure Cave all reset on the first loss. It triggers on the third attempt, not the second, because the first loss and first retry are the game's normal tension; a second loss on the same level is where a player is actually stuck. It never adds coins, so the 100-coin continue keeps its value. The test also includes a cheaper 50-coin continue on the third attempt, reusing an existing item; if it performs as well, it is the simpler option to ship.
Experiment
Population: players past level 20 who start a third attempt on the same level, randomised at user level at that moment, run for two to three weeks so every group passes through the same event rotation.
| Group | What they see on the third attempt |
|---|---|
| Control | Current experience |
| Test A | Comeback Shield |
| Test B | Continue at 50 coins |
Group
Control
What they see on the third attempt
Current experience
Group
Test A
What they see on the third attempt
Comeback Shield
Group
Test B
What they see on the third attempt
Continue at 50 coins
Read-out: Test A against Test B shows whether players are reacting to lost progress or to the continue price. If B matches A, the existing continue at a lower price is enough.
Primary outcome
Return within 24 hours after the trigger
Longer-term outcome
D7 retention from the trigger
Monetization guardrail
Revenue per user
The full table below adds the secondary metrics and decision rules behind each of these.
| Metric | Why it matters | Decision rule |
|---|---|---|
| Return within 24 hours after the trigger | Primary: does the player come back after being stuck | Meaningful lift vs control |
| D7 retention from the trigger | Primary: does the effect last | Meaningful lift vs control |
| Attempts until the level is passed | Shows whether the shield helps or only delays | Directional read |
| Revenue per user, all sources | Monetization guardrail | No material decline |
| Continue purchases and first-purchase conversion | The shield could remove the reason to pay | Net revenue decides, not continue revenue |
| Event participation and completion | Restored progress could flatten event pacing | No material decline |
Metric
Return within 24 hours after the trigger
Why it matters
Primary: does the player come back after being stuck
Decision rule
Meaningful lift vs control
Metric
D7 retention from the trigger
Why it matters
Primary: does the effect last
Decision rule
Meaningful lift vs control
Metric
Attempts until the level is passed
Why it matters
Shows whether the shield helps or only delays
Decision rule
Directional read
Metric
Revenue per user, all sources
Why it matters
Monetization guardrail
Decision rule
No material decline
Metric
Continue purchases and first-purchase conversion
Why it matters
The shield could remove the reason to pay
Decision rule
Net revenue decides, not continue revenue
Metric
Event participation and completion
Why it matters
Restored progress could flatten event pacing
Decision rule
No material decline
Rough sizing, illustrative only, not a forecast: if 100,000 players start a third attempt on the same level in a week and the shield lifts 24-hour return by 2 percentage points, about 2,000 more players return that week. The value is their later play and spending, which the D7 and revenue metrics capture.
What I would check with internal data
My play data comes from one account, so four queries should confirm or reject the premise before anything gets built:
Falsification check
If query 2 shows no drop in return after consecutive losses, or query 1 shows that lost progress does not change session endings, the Comeback Shield should not be built.
Risks and limitations
The main risk is that removing the pain of a loss also removes a reason to pay. Every mitigation keeps the shield narrow and measures net revenue rather than assuming the effect is free.
| Risk | Why it matters | Mitigation |
|---|---|---|
| Fewer continue purchases | The stacked loss may be what sells continues | Shield never saves the level itself; net revenue decides, Test B isolates price |
| Streak events lose meaning | No-fail events depend on failure having a cost | Only from the third attempt on a level; at most three levels per day |
| Players lose on purpose | Two deliberate losses could unlock the shield | It only restores what the player had before; losing on purpose gains nothing and costs two lives |
| Event pacing shifts | Restored progress may let more players finish events | Event completion tracked as a guardrail; caps tuned per event |
Risk
Fewer continue purchases
Why it matters
The stacked loss may be what sells continues
Mitigation
Shield never saves the level itself; net revenue decides, Test B isolates price
Risk
Streak events lose meaning
Why it matters
No-fail events depend on failure having a cost
Mitigation
Only from the third attempt on a level; at most three levels per day
Risk
Players lose on purpose
Why it matters
Two deliberate losses could unlock the shield
Mitigation
It only restores what the player had before; losing on purpose gains nothing and costs two lives
Risk
Event pacing shifts
Why it matters
Restored progress may let more players finish events
Mitigation
Event completion tracked as a guardrail; caps tuned per event
Additional considerations
| Risk | Why it matters | Mitigation |
|---|---|---|
| Already tested | Peak may have tried similar softeners | Frame as a narrow test with a cheaper existing-item variant |
Risk
Already tested
Why it matters
Peak may have tried similar softeners
Mitigation
Frame as a narrow test with a cheaper existing-item variant
This is a one-player study with a large but self-selected review sample; its job is to generate a testable hypothesis, not to prove one.
Also worth noting
Sources
Accessed October 2026. "Negative" means 1 to 2 stars. Game comparisons use App Store reviews only, so both games come from the same source.