|
|
|
|
|
by joenot443
385 days ago
|
|
This sort of notification-barrage is a common problem in mobile apps with multiple teams and I really wish it wasn’t. I still use Facebook quite a bit and I’m consistently frustrated by how degenerate the concept of a “notification” has become. Some of the finest engineers I know work at Meta, I know it’s not a technical problem, I think it’s an organizational problem. For example… Team A ships feature X and sets their KPI to some arbitrary measure of engagement. They miss, obviously, but instead of regrouping and hitting the drawing board, A doubles down and pressures Team B to point towards X in feature Y. A sees some marginal level of gain in engagement for X, obviously, so the intervention is deemed a success. 6mos later, Team A is asked to return the favor and add a modal pointing to new feature Z, per the request of Team B. I don’t really know what the solution is except outside of careful org-wide watchdogging to ensure this sort of user-hostile engagement infighting gets nipped in the bud. |
|
"The best minds of my generation are thinking about how to make people click ads. That sucks." - Jeff Hammerbacher