DEV Community: Tanya К. Hezzl Games

Why Ecosystem Integration Doesn’t Automatically Drive Product Adoption

Tanya К. Hezzl Games — Tue, 24 Feb 2026 20:45:37 +0000

Launching a new service inside your existing ecosystem feels like a shortcut.

Users are already logged in.
They trust the brand.
There’s no acquisition cost.

So growth should be easier.

In practice, it rarely works that way.

At Hezzl Games, we surveyed 3,000+ digital service users to understand what actually happens when a new section appears inside a product people already use.

The result: structural presence ≠ behavioral adoption.

Users Don’t Explore Interfaces Without a Reason

When asked how they react to a new section inside a familiar service:

35.7% check it out out of curiosity

42.5% try it if there’s a bonus

21.8% ignore it unless they need it

One in five won’t open it at all.

Users open products to complete tasks, not to explore architecture. If the new service doesn’t help with their immediate goal, it becomes invisible.

System Suggestions Don’t Override User Agency

When the product suggests switching:

12% follow the recommendation

76% evaluate it but decide independently

11.9% dislike automated guidance

Most users don’t outsource navigation decisions — even inside the same brand.

Adding a visible CTA is not the same as creating intent.

“Unified Ecosystem” Is a Strategy Term, Not a Behavioral Driver

When multiple services share unified progress:

25.3% like the idea

57.8% are fine with it if it’s convenient

16.8% don’t care

Convenience matters. Structure alone doesn’t.

If the new service introduces friction — additional steps, new flows, re-learning — ecosystem logic doesn’t compensate.

Trial ≠ Adoption

48.1% are willing to try a new section.

But growth is not first-click traffic.

Growth is repeat behavior.

If the service is not embedded into the user’s existing flow, the first visit becomes a metric spike — not a usage shift.

Your Real Competitor Is Existing Behavior

If similar functionality exists elsewhere:

49.5% choose better value

25.5% choose simplicity

25% choose familiarity

A new internal service doesn’t compete only with the market.
It competes with established habits.

And habits are expensive to replace.

Product Implications

If you’re building cross-service growth inside an ecosystem:

Design transition points, not just navigation links.

Measure repeat usage, not just first entry.

Test behavior without incentives to see if structural demand exists.

Reduce friction to near-zero before expecting switching.

An ecosystem can amplify behavior.

It doesn’t create it from scratch.

Based on a survey of 3,000+ digital service users conducted by Hezzl Games.

Daily Active Users Don’t Grow from Deadlines Aloneм

Tanya К. Hezzl Games — Fri, 20 Feb 2026 18:16:39 +0000

Many product teams try to increase daily activity using time pressure: streaks, expiring bonuses, limited-time rewards.

The logic is simple: create urgency → increase frequency.

We tested whether a single mechanic can explain high daily usage.

The Baseline

In a survey of 3,000+ digital service users:

82.6% reported logging in daily

65.8% said they return even after missing a day

This is not reactive behavior.
It is a stable pattern.

If daily activity reaches 82.6%, a single trigger is unlikely to explain it.

What Drives Daily Return

Users reported the following motivations:

70.7% — reward or visible benefit

65.8% — integration into daily routine

64.8% — using a bonus before expiration

51.9% — progress and accumulation

None of these factors individually reaches 82.6%.

This means daily activity cannot be reduced to one growth lever.

Urgency Is an Accelerator, Not a Foundation

64.8% respond to deadlines.

But daily activity is 82.6%.

Even under maximum overlap assumptions, urgency alone cannot account for the full daily rate.

Deadlines increase intensity.
They do not generate structural habit.

A Layered Model of Daily Engagement

The data suggests four interacting layers:

Value layer — visible benefit (70.7%)

Routine layer — embedded daily scenario (65.8%)

Accumulation layer — progress continuity (51.9%)

Intensity layer — time-based triggers (64.8%)

Daily active usage emerges when these layers reinforce each other.

When only the intensity layer exists, frequency depends on constant stimulation.

When value and accumulation are embedded, frequency stabilizes.

How to Test This in Product

Instead of optimizing a single lever, test structural sensitivity:

Remove deadlines → measure change in frequency

Reduce progress visibility → measure retention

Modify reward structure → compare DAU impact

Reduce reminders → evaluate organic return

If DAU collapses after removing urgency, urgency was masking weak structure.

If frequency remains stable, the routine is embedded.

Limitations

The data reflects self-reported motivations, not behavioral logs. It provides hypothesis direction, not causal proof.

Conclusion

82.6% daily engagement cannot be explained by a single mechanic.

Urgency accelerates.
Accumulation extends.
Routine stabilizes.
Value sustains.

Daily active users are not triggered.

They are engineered through interacting behavioral layers.

Superapps Show Scale. But Where Is the Daily Usage?

Tanya К. Hezzl Games — Fri, 20 Feb 2026 15:32:20 +0000

Superapps are usually evaluated through size.

Users.
GMV.
Orders.
Revenue.

But size does not automatically mean frequency.

I reviewed the 2024 public reports of Grab, Shopee (Sea), Revolut, Kakao, and Alibaba to check one thing:

Do they disclose how often people actually use their apps?

What Companies Publicly Report

Grab reports around 41–42 million Monthly Transacting Users (MTU).
MTU means users who made at least one transaction per month.

Shopee reports roughly 10.9 billion orders and around $100B in GMV.
That measures transaction volume.

Revolut reports 50+ million customers and profitability.
That measures customer base and financial performance.

KakaoTalk reports over 90% penetration in South Korea.
That measures reach.

Alibaba reports hundreds of millions of annual active consumers.
That measures yearly activity.

All of these metrics describe scale.

None of them describe daily behavioral intensity.

What’s Missing

Across these reports, comparable metrics like:

– Daily Active Users (DAU)
– Weekly Active Users (WAU)
– Average sessions per user
– Frequency of core actions

are not consistently disclosed.

MTU = at least once per month.
Annual active = at least once per year.
GMV = transaction volume.

These metrics don’t tell us whether the product is part of a daily routine.

Why Frequency Matters

An ecosystem can grow in revenue and transactions while usage remains event-driven.

High GMV can be driven by:
– promotions
– seasonal campaigns
– concentrated shopping events

But daily habit is a different layer.

If an app is embedded in everyday behavior, frequency becomes structural.
If not, growth depends on recurring incentives.

Public reports focus on scale because it is comparable and investor-friendly.

Frequency is harder to standardize — and therefore less visible.

The Practical Takeaway

When evaluating a “superapp,” ask:

Is it large?
Or is it daily?

Public metrics often answer the first question.

They rarely answer the second.

Until frequency becomes a standard disclosure metric, scale will continue to dominate the narrative — even when habit depth remains unclear.