I often notice that in many applications (services, information directories, etc.) authorization is implemented, whether through the application itself or through social networks. The question is why this should be done if the application is simple, well, or does not carry the need in itself ( view from the novice developer ).

Well, let's say it was decided to implement authorization in my application. How can we use this information for ourselves (pull out emails and do a newsletter for example)?

Closed due to the fact that the issue is too general for the participants Max Mikheyenko , Kromster , pavel , cheops , Denis 21 Oct '16 at 6:38 .

Please correct the question so that it describes the specific problem with sufficient detail to determine the appropriate answer. Do not ask a few questions at once. See “How to ask a good question?” For clarification. If the question can be reformulated according to the rules set out in the certificate , edit it .

  • For example, after logging in via social networks, throw information about the software onto the wall. \ n 2) use chat or rating 3) to save stories in the software so that in the future the client on the new device will download its data - Senior Pomidor
  • Authorization is needed only if needed. To do it anyhow was - this is unreasonable with respect to the user + I think there will even be a minimal chance to overwhelm the app review. And most likely they do authorization to collect max information on users. Previously, it was done for the balls on the social network, but now a different approach to this is used everywhere - markov

2 answers 2

Collect statistics, I guess. Watch how many people use the application, their personal data (gender, age, location), and already using this data you can change the interface, styles any, well, or add new functions.

  • one
    firebase will collect such data from without authorization) - iFr0z
  • @ iFr0z to master it as it should) is it generally difficult to implement it in an application? - Morozov
  • @ iFr0z, not every developer uses only ready-made solutions, many who love "bicycles") - Nikolay
  • one
    @VadimMorozov netpeak.net/ru/blog/ ... there is nothing difficult, believe me :) just click the mouse so to speak without additional code collects: first_open, in_app_purchase, user_engagement, session_start, app_update, app_remove, os_update, app_clear_data, app_exception, etc. - iFr0z

If the application has some kind of data that can (or should) be assigned to a specific user (userId), then authorization is needed accordingly. I see no other reasons.