Clear example of system-first UX – KakaoMap - Korea No.1 Map Review

A two tips: 1. Responsiveness is key: KakaoMap does not prioritize responsiveness over fidelity, an issue. 2. Think about what the user needs to see on a page, not what looks good on that page. For example, on the route map, "하지" does not provide all necessary information for the user to take a physical action based on that UI - they require the stop name as well. This is a problem throughout the application: prioritize the user, not the visual design of the application. There are dozens of examples of this trade off. Perhaps you should endeavor to hire a trained user experience designer to help orient your application around your users instead of the designer who created your UI assets. 3. The threshold for viewing and access stops on a map directly has changed, the user now needs to be further zoomed in. This is a UX mistake: the primary use cases of this app are driving directions and public transit - especially because responsiveness has decreased so significantly, stop location information should be more readily available at a higher zoom level, improving the user experience by making necessary information more accessible.
Review by Omgpvd on KakaoMap - Korea No.1 Map.