{"id":3584,"date":"2016-03-18T15:35:00","date_gmt":"2016-03-18T20:35:00","guid":{"rendered":"http:\/\/neosmart.net\/blog\/?p=3584"},"modified":"2016-03-18T15:35:00","modified_gmt":"2016-03-18T20:35:00","slug":"a-lesson-in-stupid-ui-choices-courtesy-of-facebook-messenger","status":"publish","type":"post","link":"https:\/\/neosmart.net\/blog\/a-lesson-in-stupid-ui-choices-courtesy-of-facebook-messenger\/","title":{"rendered":"A lesson in stupid UI choices, courtesy of Facebook Messenger"},"content":{"rendered":"

\"Messenger\"<\/p>\n

Facebook Messenger, from the team notorious for using 18,000 classes to create a simple iOS app<\/a>, is back to teach you one more lesson: how to stupidly use up as much valuable screenspace as possible:<\/p>\n

 <\/p>\n

 <\/p>\n

\"Facebook<\/a><\/p>\n

<\/p>\n

Obviously someone at Facebook is ridiculously proud of the toolbar that takes up half the available horizontal screen space for composing the message, so let’s take a moment to stare in awe at the beauty, elegance, and complete pointlessness of the in-band toolbar responsible for such a waste of space:<\/p>\n

\"FB<\/a><\/p>\n

Now that we have finished admiring this masterpiece, can we please get our screen real-estate back? Coming from a company as supposedly “mobile first” as this one, it’s a real surprise they couldn’t\u00a0make their native web interface properly responsive in a way that actually<\/em> matters (no, gimmicks and special effects don’t count).<\/p>\n

All of Facebook’s online web properties take advantage of1<\/a><\/sup> – and we’re expected to believe this was the best they could come up with?<\/p>\n

  1. One could probably, accurately say simply for the sake of taking advantage of…) javascript, client-side rendering, and general page bloat to a far greater extent than any other online\/web\/mobile entity out there ((Have you tried searching in FB recently? 32GiB of RAM can’t keep up w\/ how bad their client-side code is! ↩<\/a><\/p><\/li><\/ol>","protected":false},"excerpt":{"rendered":"

    Facebook Messenger, from the team notorious for using 18,000 classes to create a simple iOS app, is back to teach you one more lesson: how to stupidly use up as much valuable screenspace as possible:    <\/p>\n","protected":false},"author":505,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_feature_clip_id":0,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_post_was_ever_published":false},"categories":[1],"tags":[917,320,916,230],"class_list":["post-3584","post","type-post","status-publish","format-standard","hentry","category-software","tag-bad-design","tag-facebook","tag-facebook-messenger","tag-ui"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t