The steelman case for this is something like, mature apps that found product market fit are often over-staffed and doing a lot of duplicated work. You could get five of them together and consolidate their infrastructure/code to reduce costs, and have generalist devs who can work on any of those codebases. Then you need fewer people.

So this isn't an irrational thing to do. It's commonly done by firms like Google or Meta where they buy a small company and then rewrite it onto their own infrastructure to reduce costs. Sometimes the engineers are reallocated to other projects, or things drift and there are eventually layoffs. Google bought DoubleClick and then laid off 50% of the staff! Twitter didn't consolidate products but was clearly overstaffed, nobody imagines that Twitter was unique.

So the bull case for this is that it's finding efficiencies. The apps may not be the shiniest hottest things anymore, but they can still live on and be maintained if they're run more efficiently as a business. And yes this may involve layoffs or price rises, as often software startups hopelessly misprice their product and prefer to burn VC money than lose users or colleagues. Managers who aren't emotionally attached to the product or company can correct this, putting it on a long term stable path. That may suck for the user but probably sucks less than the company being under, or being acquihired and the product totally shut down.