java - ContentProvider vs Activity -

I have a question, currently a group of friends are developing an Android app. When we access data handling between apps, then we choose a ContentProvider . But a man told us that it is better to use the intent to open an activity and then return the data to the activity. setData (bundle) ; way. I do not have any idea that this is a good practice, but I would like to know what do you think?

Is it really a startActivityForResult ContentProvider .?.

Thank you very much

Edit

I'm going to add a little example on this:

We have a scenario where the main app needs to use data from other apps to do some processing and on the main app and then show information in the main app view

The content of each app Instead of using it, God has started a startActi VityForResult () and then set the result on setResult (bundle)) Each activity was triggered.

Instead of using each of the ContentProviders, the app is required to process data To start another application, to start using a startActivityForResult () and then set the result on setResu triggered the Lieutenant (bundle) method of each activity.

If "to start other applications to process data," you "to show the user an activity, to allow the user to interact with the data" , Then the use of an activity is entirely appropriate. The result of bringing the activity back is also appropriate, if the issue behind the activity is to select something for the user.

However, by "launching other apps to process data", you literally mean that the other app is not showing anything, but "data" To process ", then an activity is a ridiculous option. Is there a better approach than a ContentProvider a service , what does "process data" mean and some will depend on what type of results are coming back, but either better To use an activity.