> "A really bad example for not fulfilling the functional aspect when it comes to consumer software is Facebook. You need one app to use the platform that serve

> "A really bad example for not fulfilling the functional aspect when it comes to consumer software is Facebook. You need one app to use the platform that serves the news feed, and another one to use the chat function, even though the web app offers both functions at the same url." This isn't a very compelling example because the division between the Messenger and Facebook mobile apps is an intentional UX choice. It makes Messenger feel like other messaging apps on phones, e.g. by allowing instant access from the home screen to the conversation list and by reducing the app's memory footprint so it launches faster. It may not be the UX trade-off you want, but presumably Meta has data that shows mobile Messenger users prefer this. (Personally I do — it would be annoying to launch all of Facebook to reply to someone's message.)