I'm curious how big of a factor a consistent core team is to having long-term sustainable and stable software. When companies have people rotating on projects constantly and the original vision and design principles of the product are lost or changed, I can only imagine that contributes to the problem.
I've tried to retrain myself to open Obsidian (and have Obsidian configured to always jump straight to my daily note upon opening) if I compulsively pick up my phone. From there, I'm either going to write about what I'm actually trying to accomplish in the moment, or realize I had no real goal and just compulsively picked up my phone as happens more often than I'd like. It's then much easier to just put my phone back down instead of getting locked into browsing random internet streams, or I just do whatever thing I actually got my phone out to do.
I've injected some intentional friction into an otherwise compulsive habit, which opens up the opportunity to redirect that behavior. It's been very a helpful switch so far.
Not to mention it prevents people trying to legitimately access these services from doing so by putting extra barriers in place, defeating the purpose of the assistance program in the first place.
Perhaps there is something to be gained by being forced to slow down anyways. Speed for the sake of speed isn't always the highest priority. Certainly there are contexts where "keeping up" is a priority, but not always.