3 ms·
I think another lesson to learn is "if it isn't broken, don't fix it". I think we all have used apps where we got used to one thing and then there's a UI design
by godelski 8y ago
I think another lesson to learn is "if it isn't broken, don't fix it". I think we all have used apps where we got used to one thing and then there's a UI design that changes everything.
As an example that really has no major impact (but I think illustrates subtle changes), I got mad with the Android 9 update. The number one thing I was mad about was the clock placement. Every previous generation it had been placed in the upper right. Since 9 it moved to the top left (same as iPhones). Problem being that Android literally trained the userbase to look in a specific area for that feature and then moved it. Sure, I know where to look now, but I still frequently look at the top right first.
Feature changes like this I don't understand. I can't understand how it would be a significant factor in converting users (which in this case the platform had majority market share) and also results in confusing (rightly so) the existing userbase.
Not working in UI I see them a lot like QC (but with more work to do). If everything is working perfectly QC should have nothing to do. Just like if your UI is good then it shouldn't be changed. I don't understand this "need" to always change things. Sure, there are legit reasons to do so (just like QC NEEDS to exist (for the love of god don't get rid of QC)), but I see a lot of changes that happen that don't make things easier and appear (from the user side) to just be change for the sake of change.