Stories
Slash Boxes
Comments

SoylentNews is people

posted by martyb on Sunday January 09, @04:44AM   Printer-friendly
from the green-with-envy dept.

https://medium.com/@_sdc/how-apple-taught-its-users-to-hate-android-through-subtle-design-cues-518cd7eda80

If you use an iPhone, you might have noticed that SMS conversations (green-bubbles) are harder to read than iMessage conversations (blue bubbles). That's not by accident — in fact, green bubbles weren't always so difficult to read.

You've probably heard of the green and blue text message bubble colors inside the iOS Messages app. On an iPhone, normal SMS text messages are colored green, while iMessage (Apple's iPhone-exclusive chat platform) conversations are colored blue. Many iPhone users shun the "green bubble" due to the fewer features provided by SMS. If you own an iPhone, you may feel the same frustration when trying to read a green-bubble chat, as they often feel harder to read than blue-bubble chats. That's no accident.

To begin, we have to take a trip back to 2011. As you may know, iMessage, along with the signature blue bubble, didn't exist until the release of iOS 5. Before iMessage was introduced, every message in the Messages app was green, as the only messaging supported at the time was SMS. Once they added iMessage to the Messages application on iOS, the blue bubbles came along with it to help differentiate between iMessage and SMS. Given that the Messages app has stuck with the same green bubble/blue bubble differentiation, it may sound like the hatred towards SMS isn't related to the color at all. However, along the way from iOS 5 to now, a tiny design change opened a user-experience chasm between SMS conversations and iMessage ones. This isn't a story about about the green or blue colors themselves — rather, it's a story about contrast, and its astonishing impact on our perceptions.


Original Submission

 
This discussion has been archived. No new comments can be posted.
Display Options Threshold/Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
  • (Score: 2) by Magic Oddball on Monday January 10, @02:16AM (1 child)

    by Magic Oddball (3847) on Monday January 10, @02:16AM (#1211380) Journal

    And that's why customizability matters. The thing that cannot be configured by the user will be exploited against the user. … Tried with the newest KDE, and their new file manager considered that it will be beautiful to display all folders full of images with live-generated thumbnails. Even this folder with >60K PNGs with microphotography results, 10MB each.
    So after I killed the file manager as it used up a whole RAM, swap and temporary space for thumbnails, I returned to KDE3 fork.

    That has nothing to do with the extent of customizability, as you could easily have solved the problem in a couple of clicks by either:

    a) Turning off the "Show Previews" option in the View menu.

    or

    b) Opening the Dolphin Preferences dialog box, clicking the 'Previews' tab, and unchecking 'images' from the list.

    or

    c) On the same tab, setting "skip previews for local files above:" to whatever small number floats your boat.

    A GUI can have preferences up the wazoo, but it doesn't do any good if the user can't be bothered to even look in the menus or settings dialog box for them.

    Starting Score:    1  point
    Karma-Bonus Modifier   +1  

    Total Score:   2  
  • (Score: 1) by khallow on Tuesday January 11, @05:51PM

    by khallow (3766) Subscriber Badge on Tuesday January 11, @05:51PM (#1211831) Journal
    Looks like AC resolved that matter with d) a couple of clicks and a return to KDE3 fork.