Random Thoughts – Randocity!

Rant Time: Snapchat’s update failure

Posted in best practices, botch, california by commorancy on February 14, 2018

In business, the quest is always to provide the best most consistent user interface (UI) and the easiest user experience (UX) possible. Sometimes, that doesn’t always work as planned. Sometimes, it outright fails and backfires. Let’s explore.


Before 2014, Flickr had a very useful grid layout. Sometime during 2013/2014 Marissa’s then team decided to “reinvent” Flickr. They gave it a facelift and then rolled it out to much user ire. While it’s every company’s right to make design changes to their application as they see fit, it can also spell doom to an application. Flickr was no exception. After Flickr updated their app in 2014, this drastic UI change immediately drew the anger of thousands of Flickr users. Yet, Flickr still hasn’t changed anything substantial in spite of the massive number complaints. The UI is still the disaster it was designed to be and does not in any way offer what it formerly did.

The formerly well spaced grid layout was convenient and easy to use in that it showed how many views of each photo at a glance. With the new tight grid interface of random sized images, you now have to drill into each and every photo separately to find the views of that specific photo. Sure, you can use the statistics page to see which photos are most popular or most interesting, but that’s of little concession when you simply want to see how well your most recent photos are doing at a glance. In short, the latest Flickr interface introduced in 2014 still sucks and Yahoo has done nothing to right this wrong. I’d venture to guess there are fewer users using Flickr now than ever, particularly with newer apps such as Instagram, Snapchat and Facebook… and speaking of Snapchat…

Snapchat’s Update

As of February 10, 2018 and taking a page from Flickr’s playbook, Snapchat decided to roll out a brand new interface to its app. An update that has, just like Flickr, drawn the ire of many of its app users. Some users are lamenting this new interface so much, they are seriously contemplating app deletion. Because of the app’s unannounced surprise layout, some Snapchat users were unable figure out how to post causing them to lose their streaks (a way to measure how many consecutive days a user has posted). Some users streaks have been running for several hundred days. Others are just ranting about what they don’t like about it. Here’s what some Twitter users are saying:

What a disaster. Do these companies even perform basic usability testing before a release?

Design Fails

The old saying goes, “If it ain’t broke, don’t fix it”. Literally, what problems was Snapchat trying to solve with this update? If you’re planning on a UI and UX redesign, you better throw in some bones for the users to go with it. Give people a reason to want to use the interface and they’re willing to overlook other minor inconveniences. Without such bones, it ends up as merely a change for change’s sake without offering up any useful new features. Burying UI components in ever deeper layers is not more UI efficient and does not offer up a better user experience. I’m not even sure what Snapchat was thinking when they decided to roll out this UI update.

Test, test and more testing

Here’s where the rubber meets the road. If you make a UI/UX change without adding anything useful into the app for the end user, what have you accomplished as a designer? The answer is, nothing. As a designer, you have failed. Changing a UI design requires careful consideration, even more careful planning and product usability testing. This means actually giving your app to your primary target demographic and letting them use it for a few days. Let them tell you what’s wrong with it, what they like and what they dislike. Do this long before putting the new update in the app store for general release. If you do this, you can avoid the problems that Flickr and Snapchat faced with their UI and UX redesigns. If you don’t do this, you end up in the news. Failure is not an option, but so many companies fall into this trap not really knowing how to get out of it.

Rollback Plan

If the Tweet above is true regarding that support team reponse stating that there is no way to roll back, then that’s a failure on the part of the application’s designers. You should always design a rollback plan into your releases. You can’t know what may fail as a result of a release, so offering a rollback plan should always be part of a release.

If you fail to test and fail to include a rollback plan, you’ll end up just like Snapchat (and Flickr) … that is, in the news for all the wrong reasons. What this says is that the Snapchat design team should be fired and replaced. Failure is not something any company needs to endure, especially when that failure is so visible and makes your company look inept…. and it was all preventable. In this day and age, there is absolutely no reason why companies release software into the wild that angers its user base in this way. Seriously, that is such an amateur move, it’s a wonder such companies even remains in business. Worse, after such a seriously amateur move and after the dust settles, you may not have much of a business left. Your app is your lifeblood. Screw it up and you’re done.


Snapchat clearly doesn’t understand its audience. Teens are some of the most finicky users on the planet. It doesn’t take much for them to dump something and move onto the next better thing. Changing a UI interface that angers so many of them is the quickest way to lose the userbase you’ve spent so much time and effort attracting. Perhaps Snapchat will realize its mistake and correct it pronto? Perhaps it will pull a Flickr and let users suffer through with the horrible new design and not change it. With Flickr, Yahoo at least had some leverage because of all of the professional photographers entrenched in the service. Where would they go? With Snapchat, the company does not have this luxury. Snapchat isn’t a required service like Flickr is to professional photographers. This fail could easily lead to the demise of Snapchat.

It’s time for Snapchat to seriously consider all of its options here, but let’s hope they come to the right decision and rollback the interface and rethink it’s UI and UX design. Best of all, maybe they have learned a valuable lesson in software design… test your interface on your primary demographic before you ever consider a release.


Rant Time: iOS 9.1 and iCloud Backup == Fail

Posted in Apple, botch, business by commorancy on October 27, 2015

icloud_icon_brokenThis rant will be relatively short and sweet. I recently upgraded my iPhone to iOS 9.1. Not only were there some stupid issues around their new and improved upgrade process, iCloud backup is entirely broken. Let’s explore.

Pre-upgrade problems

Apple has introduced an upgrade after-hours process. What that means is that you need to agree to some terms and then the iPhone will upgrade between 2AM and 4AM as long as your phone is plugged in. I thought, “yay” until I got the agreement screen at which time I promptly yelled, “what the hell?”. Let me explain…

Apple forces on top of all else this automated upgrade agreement screen. It even disables the home button so you can’t get out of that screen by accidentally pressing the home button (like that would ever happen). That means you’re firmly planted on that screen (or so it seems). Anyway, on the agreement screen, you have to type in your Apple login credentials to verify you and to help you with that process, the iPhone conveniently pops up an on-screen keyboard like it typically does. Except, the Apple developers forgot one crucial detail. They forgot to give you a way to get rid of the keyboard when you’re done. Pressing the Enter button at the bottom right of the keyboard does absolutely nothing. The keyboard remains firmly planted on top of, you guessed it, the submit button. This means you cannot press the submit button… and, you can’t press the home button… and, you can’t do anything else.

So, now you’re literally stuck. You can’t press the submit button to complete the action and you can’t get out of this screen, or so it seems. I decided to take matters into my own hands. I pressed and held the power button until the Slide to Power Off slider appeared. Lo and behold, doing this actually made that screen go away. This entire debacle should have been my warning. But noooo. I didn’t listen to that little voice saying not to upgrade now.

Can’t use Automated Update

So now that I forced my way out of that screen with the power button, there is no way to go back in and resume the process. You’re probably wondering why I might want to do that? I had planned on hooking up a bluetooth keyboard to the phone so that on screen keyboard would not present. This would allow me to enter the data and then have access to the submit button, but noooo. Can’t make it that easy now can we Apple? So, I performed the upgrade in the normal way, by going into Settings=>General=>Software Update and used the standard method.

iCloud backup and 9.1 fail

Turn Off & DeleteTo a lesser degree, I had this same problem in 9.0.4 (or whatever the last 9.0 version was). When I attempted to backup my phone to iCloud, for whatever reason the iPhone decides to back up every app on your phone by default. Mind you, I have several gigs worth of apps on my phone on top of the 15G or so of images/videos in my library. I spent a good day working on getting my iCloud backup working on 9.0.x. It took me the better part of several hours working through stupid Settings app bugs just to get all of my apps excluded from backups. Let’s understand that Apple requires you to manually disable each and every app separately from being backed up. Let’s also understand that in order to do so, each time you click to green slider to the OFF position, you have confirm a popup that asks ‘Turn Off and Delete’ for every single app separately. Let’s consider that my phone has hundreds of apps installed. So many apps, in fact, that Settings crashes about 1/4 of the way through the ‘Turn Off and Delete’ confirmation banners. It’s an arduous task at best and it’s frustrating and aggravating at worst.

IMG_1821Yet, rolling into 9.1, Apple promptly reverts everything I spent 1-2 hours doing and now defaults back to turning every app ON (see left image) for backup yet again. How do I know? I get that very annoying ‘Not Enough Storage’ notification on my lock screen. I spent valuable time setting all of that up and Apple promptly forgets my settings. The very definition of bad user experience (UX). Instead, this time I can’t even stop the backups of any apps. Apple only gives 5GB of data storage for free. I had all of my devices comfortably making backups on iCloud using maybe 3.1GB total (4 devices), after the excruciatingly aggravating task of finally excluding all of the unnecessary crap that Apple insists on including. Perfect… until 9.1.

Now, I’m in a catch 22. I can’t make a successful backup because iOS continually resets all of my apps and forces me to back up everything to the iCloud the first time. Yet, iOS won’t allow me to change settings to deselect the apps because it must have a successful backup first. FAIL. You can go try to deselect apps, but that’s all for show. It doesn’t actually work. Oh sure, the green ON buttons turn OFF, but it’s not as if that actually works. It doesn’t respect that those apps are now OFF and the backup fails. Once it fails, all of those buttons you’ve spent tons of times clicking to OFF will all be automatically reenabled after the backup failure.

I have no idea what Apple was thinking here, but they clearly had their heads in the iClouds. This problem has gotten progressively worse with each release and has culminated in iCloud backup being entirely unusable unless you feel the urge to spend at least $1/mo for 50GB of storage so you can work around Apple’s stupid bugs. I have no intention of working around any developers bugs by spending money. Either provide workable functionality or don’t. But, there is no way I will ever spend money to a company to work around bugs in software. Apple, if you really want to force us to pay you to get more than 5GB, then just charge us up front for any space issued. Don’t beat around the bush by introducing bugs that make the freebie you’ve given become worthless. Let’s just be honest here.

If this is about spending yet more money with you to get people to buy into your iCloud storage, then just tell us that’s what you want. Don’t force us to go buy more because you want to force everything on our phones to back up. That’s not how you do it. Just change the terms and send everyone a notice that the 5GB storage you’ve issued us is no longer free and at the end of the month you lose it or you pay for it. Just tell the consumers what you want. You don’t need to do it by introduction of bugs that forces phone owners to backup everything on their phone.

Seriously… 5GB?

In this day and age when Google is giving practically terabytes of storage for free, Apple can only afford 5GB a month? Really? How much money does Apple make off of their products and they’re going to be that stingy with storage? On top of that, they force you to backup your entire 16/32/64GB phone over to iCloud. Not only is that stupid from the 5GB free perspective, it’s just asinine that I can’t control my bandwidth to this service. Seriously, I don’t want to send over 10-20GB of data across my network bandwidth. I want to control what I send and how much I send. Since I can no longer do that…

Buh Bye iCloud Backup.. it was nice knowing ya!

I’m done with iCloud backup. Not only is it stupidly designed, what real purpose does it serve at 5GB? I can backup my entire phone’s contents on iTunes on my local machine(s) as many times as I wish. There are no bandwidth constraints or disk space issues. Yet, I can barely backup my contacts on iCloud at 5GB. I have no intention of dropping $1/mo to get to 50GB, which is still only a pittance, let alone $10/mo for 1TB. Who knows how secure the data really is in iCloud? One breach and Apple will be run out of town on a rail.

I’m tired of dealing with Apple’s stupid developers who can no longer code their way out of a paper bag. I’m tired of dealing with bugs that shouldn’t even exist on a device that used to be the most intuitive device built. Now it’s a device that is merely following behind Android’s, ahem, innovation. So, I’ll happily head back to the time before iCloud existed. I’m done with that service for backups. I prefer to keep my backups local anyway. Buh Bye iCloud backups.

Apple, figure it out !

Tagged with: , , , , ,
%d bloggers like this: