Here's a way in which they can save 100% of the size: Stop stubbornly barring mobile clients from using the web interface. This is why I don't use Facebook Messenger at all.
If I request the desktop site, I am able to access Messenger (iOS, Safari)
LightSpeed: Rewriting Messenger’s codebase for a faster, smaller, simpler app
11–20 of 333 posts
Re: LightSpeed: Rewriting Messenger’s codebase for a faster, smaller, simpler app
#12Rather than reinventing the wheel, we used the UI framework available on the device’s native OS to support a wider variety of application feature needs. This reduced not only size, by avoiding the need to cache/load large custom-built frameworks, but also complexity. The native frameworks don’t have to be translated into sub-frameworks. We also used quite a few of the OS libraries, including the JSON processing library, rather than building and storing our own libraries in the codebase.
This is awesome. It shows the benefits of building an app leveraging the OS, instead of fighting or abstracting it.
Re: LightSpeed: Rewriting Messenger’s codebase for a faster, smaller, simpler app
#13Here's a way in which they can save 100% of the size: Stop stubbornly barring mobile clients from using the web interface. This is why I don't use Facebook Messenger at all.
Re: LightSpeed: Rewriting Messenger’s codebase for a faster, smaller, simpler app
#14This seems like an incredibly low bar to hurdle. FB Messenger on iOS is legendarily bloated. In the couple of weeks I had it installed it also managed to be the biggest battery drain on my phone, even more than some 3D games.
Is this incompetence or aggressive data mining? I fail to see how a texting client is that complicated...
Re: LightSpeed: Rewriting Messenger’s codebase for a faster, smaller, simpler app
#15This seems like an incredibly low bar to hurdle. FB Messenger on iOS is legendarily bloated. In the couple of weeks I had it installed it also managed to be the biggest battery drain on my phone, even more than some 3D games.
Is this incompetence or aggressive data mining? I fail to see how a texting client is that complicated...
Re: LightSpeed: Rewriting Messenger’s codebase for a faster, smaller, simpler app
#16This seems like an incredibly low bar to hurdle. FB Messenger on iOS is legendarily bloated. In the couple of weeks I had it installed it also managed to be the biggest battery drain on my phone, even more than some 3D games.
Is this incompetence or aggressive data mining? I fail to see how a texting client is that complicated...
Re: LightSpeed: Rewriting Messenger’s codebase for a faster, smaller, simpler app
#17> We accomplished this by using the native OS wherever possible
Does this mean this application does not use React Native?
Re: LightSpeed: Rewriting Messenger’s codebase for a faster, smaller, simpler app
#18I have to go years back to think of someone who told me they just couldn't take the bad UX of the clients so they deleted it.
Re: LightSpeed: Rewriting Messenger’s codebase for a faster, smaller, simpler app
#19Re: LightSpeed: Rewriting Messenger’s codebase for a faster, smaller, simpler app
#20This seems like an incredibly low bar to hurdle. FB Messenger on iOS is legendarily bloated. In the couple of weeks I had it installed it also managed to be the biggest battery drain on my phone, even more than some 3D games.
Is this incompetence or aggressive data mining? I fail to see how a texting client is that complicated...