AirFlow App - UI/UX

This a UX redesign project for an app. Let's say it's called 'AirFlow', and what it does is store in the cloud different types of files which you would normaly receive via mail/sms, only to be sent again later to another recipient. Sort of like Dropbox, but more socialy enabled.

This a UX redesign project for an app. Let's say it's called 'AirFlow', and what it does is store in the cloud different types of files which you would normaly receive via mail/sms, only to be sent again later to another recipient. Sort of like Dropbox, but more socialy enabled.
 
In this presentation I'll focus on the main screen only, as it was the most challenging to rethink and redesign.
Unfortunately, in the end it has proven to be a waste of time, but at least now i'm able to showcase it here, and maybe start a discussion with one ore two of you who have experienced something similar.
The Mockup:
In the beginning the client had some mockups that they wanted to develop (image below), but they looked more like sketches to me, which obviously were unusable. Basicaly, what they had in mind is that a user would manage the objects (tiles) by tapping + holding on one of them and then moving it to that "air symbol" menu at the top, which would open and give the user another "air logo", where they would release the selected object, attaching it to a potential mail/sms. Alternatively the same user can delete an object by draging it at the bottom, where another menu will pop up. One at a time. One at a time. I'm sure you can spot at least a dozen of problems with that, so I won't go into detail. It was definitely a challenge from the start, and that's why we have quickly decided with the team to propose a complete redesign and improve the overall UX.
Quick Sketches:
First Proposal:
Second Proposal:
Third Proposal:
After a couple of discussions with the client - we still couldn't come to an agreement. So I made a follow-up proposal with a more 'polished' UI, showcasing some of Apple's GUI guidelines, in order to prove that those mockups couldn't be turned into an usable app.
Conclusion:
The client still wasn't impressed and insisted that we stick to their mockups. So, in the end, it was ruled out as a misunderstanding between both sides, and all the proposals were dismissed. Those poor developers had to slice and implement the application from actual PDF documents that the client sent. As the result of that, it took double the amount of time to develop, and the client, of course lost money in the process. And it could have gone so much better if only the client took some time to listen to an UX Designer, who's only concern is to help in creating a better experience for the user. Isn't that what all clients should want?
 
I hope that you can take a lesson from this, whether you're a client or designer and do better next time.
Thank you!
Back to Top