[grok2]

Interesting insight with the "engagement wall" concept, but I wonder if following this idea means you spend more time in "viral" features without adding meat to your product basics. In the long run, you really want engaged customers rather than casual customers (unless perhaps you can monetize the casual users somehow).

[DenisM]

I think the point is to add features to the part of the lifecycle where you're bleeding the most users.

The desired outcome is a certain number of engaged customers, but which part of the lifecycle to target deserves serious consideration, certainly beyond the all-too-popular default choice of "let's build a feature for a fully engaged customer".