Hacker Newsnew | comments | show | ask | jobs | submit login

As I see it, two factors combine to make this to optimal strategy:

1. Limitations of Mobile UI

Facebook isn't just one tool, it's dozens of tools combined. On a web interface with PC-browser sized real estate and mouse/keyboard interactions, you can pack a lot more features onto an app and not sacrifice too much in the way of usability and complexity.

With mobile, you have to make sacrifices due to limited screen real estate. As you pack in more features into any single app, you start having diminishing returns due to increased complexity.

2. Desired Tool

So considering the limitations, you have to ask: what function does the user desire in the moment?

Consider some of the FB mobile applications: Pages Manager, Camera, Messenger.

They're all quite unique from one another. On a web interface you might be afforded the luxury of building them all into the same app with a common entry point and framework.

But in mobile, developing all those functions into a single app would be complex due to the 1st point, and unnecessary due to the 2nd.




So considering the limitations, you have to ask: what function does the user desire in the moment?

In the moment, I desire just seeing a friend's timeline while I am chatting with him and being able to go back and forth between the two. Right now I have to switch apps in order to do this. Are you saying that I am in the exception to have this use case or that I am in the exception to find app-switching inconvenient?

-----


You can still use the main Facebook app to message friends. From there, you can view the friend's timeline by clicking the information button in the upper right corner. You don't have to use the stand-alone Messenger app just because it exists.

-----




Applications are open for YC Winter 2016

Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | DMCA | Apply to YC | Contact

Search: