Profile cover photo
Profile photo
Reza Moallemi
2,037 followers
2,037 followers
About
Reza's posts

Post has shared content
No, the Floating Action Button is NOT bad UX design


And because of the bold visual style of Material Design, FABs are strikingly hard to ignore and stand out — and herein lies the problem.

That's exactly the point of a Floating Button. Given that the iconic pattern is used correctly, it isn't meant to be ignored - it's meant to stand out and be instantly identifiable and accessible. Marissa Mayer, in her approach to app design[1], states that "her people design a product for the way it will be used 98% of the time." She believes on every good product there should be a big button like that for the 98 percent use case, where if the user clicks it or taps it, they get a delightful, fluid, simple experience. 
Again, I stress on the fact the Floating Button needs to be used correctly, and if it is, it definitely does not prove detrimental to the user experience.




If you look at the screenshot of the Photos app, you’ll realise that the search FAB blocks around 50% of an image thumbnail — definitely large enough to cover a face or two.

Reading this, I thought to myself - and confirmed my thoughts with a few more users - do I really look at the bottom of the screen? I'm not defending the use of a FAB for Search, despite the fact that I find it useful, but when I'm browsing through photos or any other content for that matter, I certainly don't scan each row one by one, instead preferring to scroll when I reach the lower third of the screen. As such, I don't think the Floating Button really blocks anything important. That said, the article also brings up the issue of it blocking the bottom right corner of the list, but surely that can be addressed by adding an empty row to the bottom, can't it?




The Gmail app’s FAB is the compose button, suggesting that the primary action users perform is to create an email. But is that true? Multiple studies have shown that at least 50% of emails are now read on a mobile device, but little to none show the same shift in terms of -composing emails

Reading this, I concluded that the article is written without truly thinking the average user flow through, and doesn't address real world use cases. I concur, statistics show that a large volume of emails are read on mobile devices, however, when I receive an email, I get a push notification that acts as a CTA to open the email app, wherein I directly land on the email's page, skipping the landing page entirely. I also concur that sometimes notifications are swiped away, but the probability of an important email being swiped away is low, and if I'm going through the process of opening the email app from the launcher, the probability of my intentions being to compose an email is significantly higher, given that important emails are opened from the push notification




When FABs result in diminished UX most of the time, when it’s hard to figure out the single most-used action within an app, and when roundabout methods need to be explored (like an FAB that disappears when scrolled, or lists with differently positioned elements), I’d say the answer is a pretty resounding no

A Floating Button that hides on scroll is not a roundabout method per se. Again, used correctly, the button isn't blocking anything since it's the most used action, but it's also giving the user the freedom to make their choice. Google+ pulls this off excellently, showing the FAB when the user is engaging with the stream, and hiding it when that engagement is reversed. Don't think of it as disappearing and appearing. Think of it as two separate states - when you're engaging with your social stream, your primary action is to scroll, hence there's no FAB, and when you're not engaging with your social stream, your primary action is to post, hence the FAB.
I'd say yes. Given the 98% rule, FABs play a rather important role in the user flow, simplifying the entire process and used correctly, they can be an astoundingly helpful pattern for the end-user.


User Experience Design is a discipline of statistics, perception, psychology, testing and iteration. Every decision made is a compound result of multiple factors, and as such, it is semi-viral misleading articles that prove more detrimental to the ecosystem's experience than Floating Buttons. Developers and designers - you know your product like nobody else does. If you truly think it needs a FAB - use a FAB



[1] http://www.businessinsider.in/Marissa-Mayers-New-Rule-For-App-Design/articleshow/45994838.cms

Post has attachment
Gradle Plugin: Recently I was working on a gradle plugin for Android that makes generating versionCode and versionName automatically.
here you can find more info about it 
https://github.com/moallemi/gradle-advanced-build-version
Photo

Post has attachment

Post has attachment
I'm playing 1024 - Match Twos and Threes!. Can you beat my high score?

https://play.google.com/store/apps/details?id=com.veewo.a1024

Post has shared content

Post has attachment

Post has attachment

Post has attachment
Facebook's persistent key-value store for fast storage, forked from LevelDB rocksdb.org

Post has attachment
موتورولا موتو G رو معرفی کرده. فقط ۱۷۹ دلار!

Post has attachment
مقایسه خانواده نکسوس‌ها از ابتدا تاکنون
Wait while more posts are being loaded