Re:FacePay?
by philtar on Monday April 06, 2015 @02:17AM
(#9326870)
If you took a moment to think of use cases other than your own, you would realize that there's a lot of us that ONLY use facebook messenger. I haven't checked my newsfeed in ages.
[ Parent
| on HN ]
May I ask, why? With all the other options, including just text messaging?
Re:FacePay?
by JoelJacobson on Monday April 06, 2015 @02:30AM
(#9326893)
Good for you, and all other Messenger-only-users. But why force all other users who are using the Facebook-app to open up a separate app when they want to send or read messages?
Re:FacePay?
by testingonprod on Monday April 06, 2015 @02:34AM
(#9326904)
They expected to add a TON of complexity to the messenger product (they announced messenger as a platform at F8) and they needed a way to decouple the already complex main FB app. It buys them a bunch of things, like easier maintenance, extensibility, and ability to push updates independently among other user experience benefits.
They also didn't want to split the user experience of using Facebook messenger on mobile and hence the forced switch.
It was only a big deal because of the surface area of the world that the main Facebook product (w/ messenger) covers. I guarantee you that if Google did something like that no one would care (at least not enough to give 20,000+ 1 star reviews)
Yeah I'm one of the messenger-only people, and (obviously) I'm really happy I can use the messenger-only app, but, wow, the way they handled the integration w/ the main FB app is ungodly inelegant, almost to the level of being insulting to the user, IMO.
Re:FacePay?
by JoelJacobson on Monday April 06, 2015 @03:20AM
(#9327014)
I wouldn't call "easier maintenance" a "user experience benefit".
This reminds me of the talk "Is it really Complex? Or did we just make it Complicated?" by Alan Kay.
The complexity of the underlying problem, messaging, has not changed, but FB has made it a lot more complicated.