I often get questions about apps that are not working correctly for people and they want to know when it will be updated and what is taking so long. At times, the user has even submitted a negative review or an email directly to the app developer “days ago” and they have not seen an update yet. This seems to happen frequently with big apps like Facebook and is often met with responses from the public that resemble “Facebook can’t do anything right” or “Facebook sucks.” So, here is some insight on why Mark Zuckerberg hasn’t personally fixed your issue in the three hours since you submitted an issue.
At the start of 2009, there were 125 million Facebook users. That number was 375 million at the start of 2010, for a difference of about 200 million. That holds true, mostly, because at the start of 2012, there were 794 million users. Keep in mind that these 800 million users span multiple countries and languages. The technology required to keep them all involved in Facebook is spread across different browsers on different operating systems, mobile pages, apps - each with different access speeds. There are a lot of moving parts.
Updating an app is not as simple as fixing your individual issue. How will it affect users on an older version of iOS or Android users. Changing one piece of the app and how it pulls information affects the servers holding all the information and the connection to them. It is very much a “hip bone is connected to the thigh bone” kind of situation. Once Facebook app developers can fix an issue and ensure they haven’t broken some other connection in the process they can test the app in devices - of all platforms. When that’s done, it’s ready to be released.
But wait… like a bad infomercial at 3am… there’s more. They cannot release their own app. It gets submitted to the app store where Apple has to approve it. I can only speculate that apps like Facebook get a certain priority given their size. Even so, it is not immediate. The files that drive the app are uploaded to the app store for approval. With 794 million users and millions upon millions of those users in the mobile space using the app, the last thing Apple, for example, wants is everyone downloading the update at the exact same moment, along with all of the other apps people are downloading and updating. Carriers don’t want it either. So the relase gets staggered. When an update goes live, it gets put out a little at a time, spreading across the digital landscape until everyone has it.
With a process like that, not every problem will get addressed as they happen. Typically, developers wait for a series of issues and upgrades, unless the problem is so glaringly obviously that it can’t be ignored until the next planned release. There is no money in ignoring you. They don’t suck. It is just too big of a process to release updates for every single complaint within a 794 million user ecosystem.
Maybe that sheds some light on how it happens so you’ll understand in the future.