Most logins don't solve any of my problems, exceptions include things tied to a credit card. The more typical best case is that a login solves problems around site administration. A lot of login requirements seem to be based on logins being easy to implement in frameworks or being the designer's concept of how web sites work.

The last one is often a bit of an anti-pattern. For most websites a person who actually lands on and engages with the site is pure gold and putting friction on that interaction adds noise...there are people who won't bother to create an account in the absence of more information than can be gleaned from the 'public' resources (often because most functionality gets hidden behind the login).

More and more commonly, logins are a way of growth hacking: Look at all these email addresses that we can pretend are users and sales prospects.

I'm not mrspeaker, but I have a similar stance regarding apps/logins/etc.

For me, it is the burden of having to create accounts for stuff I'll probably only use once, plus the mental burden of knowing that the website has my personal information and might leak it.

That, and the fact that having an account/app these days is synonymous with "oh, sure, send me all the spam you have!", via e-mail or mobile notifications.

If anything, password managers help me see which accounts I should be deleting.

The stickyness of email addresses (having to update email/recovery contacts) and proliferation of user ToSes is yet another limiting factor.

Increasignly I just say "no". I've been cutting back on services and apps. It's something of a relief.