Timeline for Is it a strong anti-pattern to use a Floating Action Button in an iOS app?
Current License: CC BY-SA 4.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 17, 2022 at 12:17 | history | edited | Benjamin S. Leveritt | CC BY-SA 4.0 |
Reaffirmed statement after 6 years...
|
| Oct 17, 2022 at 11:57 | comment | added | Benjamin S. Leveritt | It's been a while since I've had to think about this. And I wouldn't say that FABs are as unfamiliar in iOS as they were in 2016. That said, I still think you have to learn what they do by committing to do the action before you know what it does. This isn't always a great experience (it might put cautious users off or push them into user journeys they're not ready for). Essentially still the same advice: use them intentionally and thoughtfully. | |
| Oct 12, 2022 at 6:43 | comment | added | RedShift | It's an abstract concept with low discoverability Can you explain this? A FAB doesn't need to be discovered, it's always there and it always does one defined obvious action. | |
| Oct 25, 2016 at 16:45 | vote | accept | Goren Berdichevsky | ||
| Oct 17, 2016 at 8:56 | history | edited | Benjamin S. Leveritt | CC BY-SA 3.0 |
deleted 6 characters in body
|
| Oct 17, 2016 at 8:39 | review | First posts | |||
| Oct 17, 2016 at 8:40 | |||||
| Oct 17, 2016 at 8:37 | history | answered | Benjamin S. Leveritt | CC BY-SA 3.0 |