Are you happy with the UX of your app? Well, we all know that we as app developers never are 100% satisfied with our work – and that’s a good thing!
Only developers that strive for perfection will come close to it.
This article may open your mind about some mistakes that you would never have recognized otherwise. Let’s not waste your time and get right started!
It’s a glorious time we live in – if you are a data enthusiast.
There are dozens of great quantity analysis tools out there (e.g. mixpanel, flurry, google analytics), providing you with deep insights into the numbers behind your app.
And while these tools are very useful, you can lose sight of how your users actually act behind the numbers.
This will result in building UX that works in theory, but may not in reality.
Quality analysis, also known as UX analytics, allows you to look at individual users at a greater detail, providing you with an understanding that you can’t get out of looking at graphs.
Use both numberdriven and user driven analysis to connect the dots – this will allow you to have an optimal base to work upon on.
You can either go for a services like usertesting.com (a bit more expensive), sessioncam.com (web only) or try out our tool (mobile only).
“Wow, that background is really eye-catching! Wait, what was the app about again?”
Making your app pretty is the right idea, but it can’t come at the cost of being clear. Finding the balance is harder than you may think.
If your background is too distracting, it can confuse the user and take the attention from what you want to say.
Or as Wojciech Zielinski said: “Whitespace is like air: It is necessary for design to breathe.”
Take a close look at the background of your app. Can you make it simpler?
You can also use heat map analysis to see if users are trying to click or gesture on the background, instead of the things you want them to click on.
Ok, so a background that is too prominent is bad. The opposite is true for your call to action. If your app is a map, then the call to action gives the direction.
The call to action button should say:
Hey, look at me, this is how we are going to proceed!
If it is not clear enough, your users will get lost and not do what you, as the developer, want.
Anywhere that you want your users to click, put up a noticeable sign that shows the way. The call to action button should be in contrasting colors to the rest of your website.
Again, you can use heat map analysis to see how often it is getting clicked in comparison to other elements in your app.
Performance is like electricity for your UX: You can’t see it, but without it, nothing would work.
It can be easy to get lost in the pure looks of your app and ignore speed and crashes – imagine being in a car that looks like a ferrari, but drives like a corsa.
A study by google showed that 53% of mobile users are abandoning sites that take longer than 3 seconds to load. Remember, you can only make your first impression once. If you annoy your users by taking a long time to load or even crashing your app, they are very likely to not be returning.
Take your time to review how your app actually is performing. How fast is the app loading? How many crashes are there?
You can use various tools to track crashes and fix them real fast.
No one likes to waste time.
Would you have continued reading this article if I would have told you about my personal and work life in the introduction? No?
It’s the same for your users! If they feel like they are going through stuff that they don’t want to go through, they stop caring.
Every unnecessary action increases the chance of your app just being closed.
How much screens can you cut?
Make it as simple as possible, look into where your users are dropping out and use that knowledge to identify and fix bottlenecks.
So that sums it up, I hope you could take something out of this – if you have other points that you would like to add to this list, feel free to comment below!