Use of monofunctional and multifunctional mobile applications?

Question

Mobile development

During the development of one of the projects, a dilemma arose:

• To increase the functionality of the application with additional functions that fit into the general scope, but have a slightly different consumption model.
  
• Separate new functions into a separate application, thereby giving the user 2 products, where each performs its task.
  

Subjectively, I can justify using each of the following:

• Easier promotion of a joint product
  
• Intended use of the application without overloading with unnecessary functions.
  

Interested in your own experience and links to studies, if any.
To expand the question, I will give examples from an arbitrary field (although the examples may depend heavily on it and I am interested in the fields of Finance, Collaboration):
Monofunctional application from the Sports category:

• Application for tracking your workouts
  
• Application for monitoring the progress of training
  
• Applications for maintaining your training program
  
• Application for with a description of the exercises
  

A multifunctional application from the Sports category, which would organically contain all these functions.
In the meantime, I continue to collect opinions:
• According to statistics, the average number of applications on smartphones is from 2 to 10, and if you collect 2 applications in 1, then the chances of lingering on the screen of your user's device increase.
• In case there is a problem with the application or one of the functions, it will pull down both your directions.
• If you have added a new set of features or a new area of ​​use to an existing product, then it will be more difficult to promote it as part of 1 application than to separate it into a separate one. (How fair this is a topic for a separate discussion)

Answer 1

It depends on the purpose for which the application(s) is created.
If, for example, the goal is monetization, and applications are not free, then of course it is better to break them into several small ones that will be easier to buy.
If this is an advertising application, then hardly anyone wants to have a separate application with a pizzeria price list, and another through which you can order pizza from the same establishment.

Answer 2

I would break into different applications. The most important advantage for me is that new buns will not constrain the old ones and interfere with their individual development.

Answer 3

I would combine of course. Many small applications are easy to support as long as there are less than a dozen of them.