@elonmusk We have done a bunch of work to improve performance and we found that it correlates well with increasing UAM and Ad spend. Agree, there is plenty of room for performance improvements on Android. However, I don’t think the number of requests is the primary issue.
@elonmusk For a cold start of the app there are ~20 requests to load home timeline. Most of the requests are non-blocking and happen in the background. This includes things like images, user settings, hashflags, etc.
@elonmusk I think there are three reasons the app is slow. First it’s bloated with features that get little usage. Second, we have accumulated years of tech debt as we have traded velocity and features over perf. Third, we spend a lot of time waiting for network responses.
@elonmusk One performance focused holdback (go/ddg/7601) showed a causal increase of 40M UAM. For reference Mixed Media only showed +10M UAM. If we want to improve things we need to make tradeoffs that favor performance over new feature work.
@elonmusk Frankly we should probably prioritize some big rewrites to combat 10+ years of tech debt and make a call on deleting features aggressively.
• • •
Missing some Tweet in this thread? You can try to
force a refresh
