谷歌maps菜单语言设置_Google Maps:拯救未来之路— UX案例研究

谷歌maps菜单语言设置

I have a lousy sense of direction, so Google Maps has always been my right-hand app. On a whim last year, I decided to skip the beach and sunburn and head to Budapest for spring break. That’s when Google Maps became my best friend.

我的方向感很差,因此Google Maps一直是我的右手应用。 去年我一时兴起,我决定跳过海滩和晒伤,然后去布达佩斯度过春假。 那时候Google地图成为我最好的朋友。

When I wasn’t admiring the Buda Castle or bathing in the Széchenyi Thermal Baths, I was on Google Maps. Google Maps helped me decide where to eat, how many attractions I could see in a day, what public transportation to take, and — when I inevitably got lost — how to get back to my Airbnb.

当我不欣赏布达城堡或在塞切尼温泉浴场沐浴时,我在Google地图上。 Google Maps帮助我决定了在哪里吃饭,一天可以看到多少景点,乘坐哪种公共交通工具,以及(当我不可避免地迷路时)如何回到Airbnb。

I learned that when I take a trip to a new area, I want to explore and engage with that place as much as possible. This is difficult because:

我了解到,当我去一个新地区旅行时,我想尽可能地探索并与之互动。 这很困难,因为:

  1. I don’t always know which places to explore

    我并不总是知道探索哪些地方

  2. I don’t know how to optimize my route to make sure I get to all of the places I want to see

    我不知道如何优化路线以确保到达所有我想看的地方

  3. I don’t know where to save my ideas and plans in one place

    我不知道将我的想法和计划保存在哪里

第一件事第一 (First Things First)

User Research

用户研究

I interviewed ten users to understand how people use Google Maps to plan daily activities. I found two distinct user-types:

我采访了十个用户,以了解人们如何使用Google Maps计划日常活动。 我发现了两种不同的用户类型:

  1. Logistic-Oriented. These are users who use Google Maps daily to optimize their routes. They like to focus on numbers: trip duration, mileage, and traffic delays.

    面向物流。 这些是每天使用Google Maps优化其路线的用户。 他们喜欢关注数字:出行时间,里程和交通延误。

  2. Explorers. These users might not use Google Maps as their primary navigation app. They use it to find things to do, pin locations they want to visit, and see what those places look like using Street View.

    探险家。 这些用户可能不使用Google Maps作为其主要导航应用程序。 他们使用它来查找要做的事情,固定要访问的位置,并使用街景视图查看这些地方的外观。

In general, both user types agreed: Google Maps is great at 1) helping you decide where to go and 2) helping you get there.

总的来说,两种用户类型都同意:Google Maps擅长以下方面:1)帮助您决定要去哪里; 2)帮助您到达那里。

Market Research

市场调查

Logistic-oriented users praised Google Maps for having the most accurate GPS information. Users also agreed that Google Maps promotes exploration more than other navigation apps.

面向物流的用户称赞Google Maps具有最准确的GPS信息。 用户还同意Google地图比其他导航应用程序更能促进探索。

A chart compares the features of Google Maps, Apple Maps, and Waze. Google Maps lacks a social component compared to Waze.
Feature comparison among top navigation apps.
顶级导航应用之间的功能比较。

Although Google Maps lets you share your route progress and favorite places with friends, it has very limited social elements — especially compared to apps like Waze. I thought this could be an interesting opportunity area. Could adding a larger social element help users find even more cool places to explore through their network of friends?

尽管Google Maps允许您与朋友共享路线进度和最喜欢的地点,但社交元素非常有限,尤其是与Waze之类的应用相比。 我认为这可能是一个有趣的机会领域。 可以添加更大的社交元素来帮助用户通过其朋友网络找到更多更酷的地方进行探索吗?

After acquiring a hefty stack of sticky notes and recruiting two friends, we got to work brainstorming ways that Google Maps could be even more useful to me on my next spring break trip.

在获得大量便签并招募了两个朋友之后,我们开始集思广益,以求在我的下一个春假旅行中,谷歌地图对我来说更加有用。

Identifying Opportunity Areas

确定机会领域

Two areas of improvement stuck out for enhancing trips to new areas:

为了改善前往新领域的旅行,突出了两个改进领域:

  1. Exploring + Connecting. This would give users even more ideas of places to visit when traveling.

    探索+连接。 这将使用户在旅行时可以更多地了解游览地点。

  2. Organizing + Planning. This would help users optimize their routes and get to all the places they want to go efficiently.

    组织+计划。 这将帮助用户优化路线,并高效到达所有想要去的地方。

With this in mind, we narrowed our potential solutions down to 4 viable features:

考虑到这一点,我们将潜在的解决方案缩小到4个可行的功能:

Pros and cons for 4 features: shared route histories, tagging friends in trips, saved routes, and calculation of trip cost.
Pros and cons for potential solutions.
潜在解决方案的利弊。

Although including friend activity might give users more ideas for places to go, user feedback helped me understand that a large social component would overly complicate a navigation app — and actually drive some users away.

尽管包括朋友活动可能使用户对去的地方有了更多的想法,但用户的反馈帮助我了解到,庞大的社交组件会使导航应用程序过于复杂,并实际上使一些用户离开。

I wanted a solution that would appeal to both the logistic-oriented users and explorers. After accounting for feasibility and impact, I chose my final solution.

我想要一个对面向物流的用户和浏览器都有吸引力的解决方案。 考虑了可行性和影响后,我选择了最终的解决方案。

定位我的目的地 (Pinpointing My Destination)

I decided to go with the Saved Routes feature.

我决定使用“ 保存的路线”功能。

Thanks to Google Maps, we have a lot of valuable information at our fingertips. After going through the trouble of finding the best route for you — shouldn’t you be able to save it for later?

多亏了Google地图,我们唾手可得了许多有价值的信息。 在为您找到最佳路线的麻烦之后,您难道不可以保存它以便以后使用吗?

到达那里 (Getting There)

Choosing an Entry Point

选择一个入口点

The first step was exploring how users would access this feature. I wanted the entry point to be visible and intuitive. However, I didn’t want it to be so prominent that it distracted from Google Maps’ main goal of getting you from point A to point B. I played around with different entry points to explore how users might save their routes:

第一步是探索用户如何访问此功能。 我希望入口点可见且直观。 但是,我不希望它如此突出以至于偏离了Google Maps将您从A点带到B点的主要目标。我在不同的入口点进行了探索,以探索用户如何保存其路线:

Screens comparing 3 potential entry points for a Saved Routes feature: A. Home screen, B. Directions page, C. Search history.
Medium-fidelity explorations for the Saved Routes feature entry point.
“保存的路径”功能入口点的中保真浏览。

I decided that Screen B accomplished this goal best. I thought putting the entry point on the home screen like Screen A might enhance visibility — but, user testing showed that it made more sense to save the route only after actually creating it. Although Screen C could serve as an additional entry point, I decided to focus on one main access point for my study.

我认为Screen B最好地实现了这个目标。 我以为将入口点放在屏幕A之类的主屏幕上可能会提高可见性-但是,用户测试表明,仅在实际创建路径之后保存路径才有意义。 尽管Screen C可以作为额外的入口点,但我还是决定将重点放在一个主要的访问点上进行研究。

Accessing Saved Routes

访问保存的路线

Examining the information hierarchy of Google Maps, I got a good feel for where a list of saved routes might fit in. The ‘Saved’ tab on the homepage seemed like a pretty logical choice to me.

检查了Google Maps的信息层次结构后,我对可能保存的路线列表适合的位置有了很好的感觉。主页上的“ Saved”选项卡对我来说似乎是很合理的选择。

Diagram of Google Maps information hierarchy. Saved Routes are assessed under the ‘Saved Tab,’ along with other saved lists.
Information hierarchy for Google Maps. Blue indicates that the branch was added for my Saved Routes feature.
Google地图的信息层次结构。 蓝色表示已为我的“保存的路线”功能添加了该分支。

Next, I wanted to explore what the ‘Saved Routes’ page might look like. I decided that it would be helpful to have folders to organize routes — but I wasn’t sure what the best layout would be.

接下来,我想探索“保存的路线”页面的外观。 我认为使用文件夹来组织路线会有所帮助-但我不确定最佳布局是什么。

Screens comparing 3 potential organization styles for Saved Routes folders.
Medium-fidelity flows for accessing Saved Routes.
中保真流程,用于访问保存的路由。

User feedback confirmed that organization is a top priority. Participants agreed that folders would help with organization, but they didn’t want to be forced to use them. They also liked the idea of sorting and searching for routes. I ended up choosing a design most similar to Screen A because it was most visually consistent with similar Google Maps features and it would allow users to filter their routes so they could find them efficiently.

用户反馈确认组织是重中之重。 与会者同意,文件夹将有助于组织,但他们不想被迫使用它们。 他们还喜欢对路线进行分类和搜索的想法。 我最终选择了一个与屏幕A最相似的设计,因为它在视觉上与类似的Google Maps功能保持一致,并且允许用户过滤其路线,以便他们可以高效地找到它们。

铺在坑洼处 (Paving Over the Potholes)

After establishing the entry points for saving and accessing routes, I turned to optimizing my flows for efficiency and visual design.

建立用于保存和访问路线的入口点后,我转向优化流程以提高效率和视觉设计。

Naming and Saving Routes to Folders

命名和保存路由到文件夹

Originally, my flow for naming and saving a route had 3 separate steps: naming a route, deciding whether to save it to a folder, and choosing a folder to save it in. User feedback showed that I could enhance this flow by combining steps.

最初,我的命名和保存路线的流程包含3个单独的步骤:命名路线,决定是否将其保存到文件夹中以及选择要保存到其中的文件夹。用户反馈显示,我可以通过组合步骤来增强此流程。

Original flow for saving routes: 1. Name route, 2. Pop-up asks if you want to save your route to a folder, 3. Select folder.
Flow that combines all 3 steps. Screen has a pop-up to name your route and a drop-down menu to select a folder if desired.
Flow combines 2 out of 3 steps: 1. Pop-up to name your route, 2. Scroll through folders to select one if desired.

Although Flow B combines all 3 steps, the pop-up is overly crowded and visually unappealing. I ended up going with a flow most similar to Flow C, which gives users more information about each folder and is easier to read.

尽管流程B合并了所有三个步骤,但弹出窗口过于拥挤且视觉上不吸引人。 最后,我使用了与Flow C最相似的流程,该流程为用户提供了有关每个文件夹的更多信息,并且更易于阅读。

Next, I focused on visual design. I made the following adjustments to make sure I was staying consistent with the Google Maps brand.

接下来,我专注于视觉设计。 我进行了以下调整,以确保与Google Maps品牌保持一致。

Comparison of 2 folder selection pages and 2 pop-ups for naming routes with focus on maintaining Google Maps visual design.
Changes in design to maintain visual consistency with Google Maps.
更改设计以保持与Google Maps的视觉一致性。

I ended up creating a Google Maps UI Kit to help me stay visually consistent. Because I’m building off of Google’s work, I knew visual consistency would be key to integrating my feature successfully.

我最终创建了一个Google Maps UI Kit,以帮助我保持视觉上的一致性。 因为我是基于Google的工作,所以我知道视觉一致性是成功集成功能的关键。

Editing Previously Saved Routes

编辑以前保存的路线

Finally, I focused on how users could edit their Saved Routes. At first, I wanted to have a prominent Edit Button to draw attention to it. Then, I realized this would be changing the flow that Google Maps has in place.

最后,我重点介绍了用户如何编辑其保存的路线。 首先,我想要一个醒目的“编辑按钮”来吸引人们的注意。 然后,我意识到这将改变Google Maps的流程。

The Ellipses Button in the upper-right corner of the screen already lets users edit!

屏幕右上角的椭圆按钮已经可以让用户进行编辑!

Comparison of 3 screens for editing Saved Routes: A. Edit Button, B. No Button, C. Highlighted Saved Button.
Medium-fidelity flows for editing Saved Routes.
中保真流程,用于编辑保存的路线。

I decided to go with Screen C. This screen maintains the editing flow that Google Maps already has by using the Ellipses Button. The highlighted Saved Button also provides feedback so users know they are editing a previously saved route.

我决定使用屏幕C。此屏幕使用省略号按钮来维护Google Maps已经具有的编辑流程。 高亮显示的“保存的按钮”还提供反馈,使用户知道他们正在编辑以前保存的路线。

到了 (Arrived.)

After polishing off my flows and visual design, it was time to put the pieces together.

在完善流程和视觉设计之后,是时候将这些片段放在一起了。

Finalized Flows

最终流程

Final high-fidelity flow for saving routes: 1. Name route, 2. Select folder, 3. Pop-up confirms your route is saved.
Final high-fidelity flow for saving routes.
最终的高保真流程,可节省路线。
Final high-fidelity flow for editing routes: 1. Click on route, 2. Click Ellipses Button, 3. Edit, 4. Click the Done Button.
Final high-fidelity flow for accessing routes.
用于访问路线的最终高保真流程。

I also created a prototype to show how users would interact with the feature within the actual Google Maps app.

我还创建了一个原型,以展示用户如何与实际Google Maps应用程序中的功能进行交互。

Google Maps is already great at helping users explore new places and helping them get there. My hope is that saving routes will allow users to take full advantage of the mapping and explore capabilities by letting them plan trips in advance. Users can then feel good about taking the time they need to create the best route for them knowing they can save it and come back to it later.

Google地图已经非常擅长于帮助用户探索新地点并帮助他们到达那里。 我希望通过保存路线,可以让用户提前计划行程,从而充分利用地图并探索功能。 然后,用户知道自己可以保存并稍后返回,便可以花些时间为他们创建最佳路线,从而感觉良好。

Thanks for tuning in to my first case study! I really enjoyed gaining design experience through Cornell AppDev’s Digital Product Design class and can’t wait to continue developing my UI/UX skills in the future. If you have any thoughts, feel free to connect— I’d love to hear them!

感谢您收看我的第一个案例研究! 我真的很喜欢通过Cornell AppDev的数字产品设计课程获得设计经验,并且迫不及待地希望将来继续发展我的UI / UX技能。 如果您有任何想法,请随时联系 -我很想听听他们的意见!

翻译自: https://uxdesign.cc/google-maps-saving-the-road-ahead-2460f0f3715a

谷歌maps菜单语言设置

本文来自互联网用户投稿,该文观点仅代表作者本人,不代表本站立场。本站仅提供信息存储空间服务,不拥有所有权,不承担相关法律责任。如若转载,请注明出处:http://www.mzph.cn/news/274564.shtml

如若内容造成侵权/违法违规/事实不符,请联系多彩编程网进行投诉反馈email:809451989@qq.com,一经查实,立即删除!

相关文章

1万小时后,我从外包走进了字节跳动,现在出了一本书,文末送书!

谨以此书献给相信“努力有用”的你by 大史不说话《 前端跨界开发指南:JavaScript工具库原理解析与实战》先做个自我介绍我是大史不说话,是一名前端工程师,一个相信“努力有用”的、不太聪明的、行动力还可以的程序员。曾经因为一篇《10000小时…

视觉设计师跟平面设计_使设计具有视觉吸引力

视觉设计师跟平面设计Interaction Design is very gratifying.交互设计非常令人满意。 From fast critical thinking to extracting ideas in tangible forms within the team is sure fun and challenging.从快速的批判性思维到在团队内部以有形的形式提炼想法,无…

ExtJs4 笔记 Ext.tab.Panel 选项卡

本篇讲解选项卡控件。 一、基本选项卡 首先我们来定义一个基本的选项卡控件,其中每个Tab各有不同,Tab的正文内容可以有三种方式获取: 1.基本方式:通过定义html和items的方式。 2.读取其他html的信息:通过设置contentEl就可以获取其他html的信…

一直刷不动算法题,怀疑人生?试试五毒掌法!

大家好,我是若川。持续组织了近一年的源码共读活动,感兴趣的可以 加我微信 ruochuan12 参与,每周大家一起学习200行左右的源码,共同进步。同时极力推荐订阅我写的《学习源码整体架构系列》 包含20余篇源码文章。历史面试系列。另外…

还在用开发者工具上传小程序? 快来试试 miniprogram-ci 提效摸鱼

1. 前言大家好,我是若川。持续组织了近一年的源码共读活动,感兴趣的可以 加我微信 ruochuan12 参与,每周大家一起学习200行左右的源码,共同进步。同时极力推荐订阅我写的《学习源码整体架构系列》 包含包含jQuery、underscore、lo…

超级玛丽马里奥版下载_将超级马里奥赋予生命

超级玛丽马里奥版下载Have you ever seen a zoetrope? If today’s sophisticated computer animation is the latest evolution of the form, then the remarkable zoetrope is a crucial ancestor; the transitional form between the drawing and the animation.等皆你见过…

如何在繁重的工作中持续成长?

大家好,我是若川。持续组织了近一年的源码共读活动,感兴趣的可以 加我微信 ruochuan12 参与,每周大家一起学习200行左右的源码,共同进步。同时极力推荐订阅我写的《学习源码整体架构系列》 包含20余篇源码文章。历史面试系列。另外…

熊kong作品资源链接_Kong雀技术:向世界展示您的设计作品

熊kong作品资源链接The door opened and I entered the bedroom of an apartment I was looking to rent. No furniture or items inside, it was almost empty except for a frame in the wall. It was a photo of a peacock. As I stared at it, I could not shake one clear…

漫谈前端工程化基建和架构设计 | 留言送书

大家好,我是若川。持续组织了近一年的源码共读活动,感兴趣的可以 加我微信 ruochuan12 参与,每周大家一起学习200行左右的源码,共同进步。本文留言抽奖送书,具体规则看文末。透过工程基建,架构有迹可循。前…

设计模式 日志系统设计_模式:我们设计系统的故事

设计模式 日志系统设计Design Patterns are some of the most over-used concepts in design today. And we all know what happens when you have some ideas all over the place. We start repeating them like parrots and applying them to everything, therefore distorti…

前端好还是后端好,看看7年前端和后端怎么说

大家好,我是若川。持续组织了近一年的源码共读活动,感兴趣的可以 加我微信 ruochuan12 参与,每周大家一起学习200行左右的源码,共同进步。同时极力推荐订阅我写的《学习源码整体架构系列》 包含20余篇源码文章。历史面试系列。另外…

提升UI技能的5个步骤

element ui 步骤重点 (Top highlight)What to do when you know how to use the software and know the basics of designing interfaces? There are a few simple things that you can do to take your skills to the next level, and you don’t need to invest in expensiv…

空降进阿里的 P10 都是什么人

周末见了几个朋友,吃饭时聊到他们前老板郭东白(阿白),对了,我朋友在速卖通,他说阿白是 14 年来的阿里,直接就空降进了他们部门,当上首席架构师,后来又升到了 CTO&#xf…

linux下练习 c++ 关联式容器multimap特性

/* multimap特性 key可以重复 不支持下标访问 */ #include<iostream> #include<string> #include "print.h" #include<map> using namespace std; typedef pair<int,string> pairmp; typedef multimap<string,double> MS;int main() …

一致性设计,而不是一致性

一致性设计重点 (Top highlight)If we ask any design system advocate what are the main reasons to build and maintain a design system, chances are ‘Consistency’ will come up as first or second in their list, together with the ‘A single source of truth’ po…

如何在 React 应用中使用 Hooks、Redux 等管理状态

大家好&#xff0c;我是若川。持续组织了近一年的源码共读活动&#xff0c;感兴趣的可以 点此扫码加我微信 ruochuan12 参与&#xff0c;每周大家一起学习200行左右的源码&#xff0c;共同进步。同时极力推荐订阅我写的《学习源码整体架构系列》 包含20余篇源码文章。历史面试系…

长语音识别体验_如何为语音体验写作

长语音识别体验重点 (Top highlight)“Voice User Interface (VUI) Designer” is an increasingly prominent job title in the tech world. A VUI designer typically writes the conversation and designs the flow between a VUI — an invisible interface that communica…

分析了1011个程序员的裁员情况后得出的启示

大家好&#xff0c;我是若川。持续组织了近一年的源码共读活动&#xff0c;感兴趣的可以 点此扫码加我微信 ruochuan12 参与&#xff0c;每周大家一起学习200行左右的源码&#xff0c;共同进步。同时极力推荐订阅我写的《学习源码整体架构系列》 包含20余篇源码文章。历史面试系…

定义设计系统

System is “the whole creation, the universe,” from Late Latin systema “an arrangement, system,” from Greek systema “organized whole, a whole compounded of parts”.系统是晚期拉丁语系统的“整体创造物&#xff0c;宇宙”&#xff0c;是希腊语系统的“一种安排…

2w行代码、200个实战项目,助你修炼5大编程基本功。【送书《设计模式之美》】...

大家好&#xff0c;我是若川。之前送了很多书&#xff0c;现在又和异步图书合作再次争取了几本书&#xff0c;具体送书规则看文末。所谓练武不练功&#xff0c;到老一场空&#xff0c;以技术为驱动的程序员同样如此。面向对象编程范式、设计原则、代码规范、重构技巧和设计模式…