ux可以去哪些公司

by Ifeoluwa Arowosegbe

通过Ifeoluwa Arowosegbe

忽略UX会如何伤害您的API以及您可以如何做 (How ignoring UX hurts your API and what you can do about it)

Creating experiences that users love is crucial to the success of any product. Companies invest lots of resources trying to make sure they have kickass landing pages and cool page transitions. Yet, these efforts are often in sharp contrast with developers’ experiences when they try to consume their APIs.

创造用户喜爱的体验对于任何产品的成功都是至关重要的。 公司投入了大量资源，以确保他们拥有kickass登陆页面和很酷的页面过渡。 但是，这些努力通常与开发人员尝试使用其API时的体验形成鲜明对比。

Quick Note: This is about APIs in the context of RESTful services.

快速说明：这是关于RESTful服务上下文中的API。

Your API is a full-fledged product. It is consumed by developers who are considered to be technically sound, but that doesn’t mean they are less-deserving of top notch, premium treatment. Developers are users, too.

您的API是成熟的产品。 它被认为在技术上合理的开发人员所使用，但这并不意味着他们不应该获得一流的优质服务。 开发人员也是用户 。

“The goal of user experience design in industry is to improve customer satisfaction and loyalty through the utility, ease of use, and pleasure provided in the interaction with a product.” — UX Curve

“行业中用户体验设计的目标是通过与产品交互提供的实用性，易用性和愉悦性来提高客户满意度和忠诚度。” — UX曲线

你赔钱了 (You’re Losing Money)

Long before a developer decides to recommend your product/service to the tech lead or company, you should know that they’ve already scoured your API documentation page. They’ve tried calling several endpoints, and have made sure that they’re comfortable — and in rare cases, happy — with your offering(s).

在开发人员决定向技术负责人或公司推荐您的产品/服务很久之前，您应该知道他们已经在API文档页面中进行了搜索。 他们尝试调用多个端点，并确保它们对您的产品感到满意，在极少数情况下，他们对此感到满意。

You lose revenue if anything (docs, response time, and so on) doesn’t meet the developer’s standards. They’d rather go in search of more desirable alternatives than stick around trying to figure out the correct way to consume your API.

如果任何内容(文档，响应时间等)不符合开发人员的标准，您将损失收入。 他们宁愿去寻找更理想的替代方案，而不是坚持尝试找出使用API​​的正确方法。

你错过了人才 (You’re Missing Out On Talent)

A study by Glassdoor shows that 61% of their users actively conduct research about a company before deciding to apply for a job there. We can only expect this number to be steeper for professional developers that have a 98% employment rate (3.9% work part-time), according to StackOverflow’s Developer Survey.

Glassdoor的一项研究表明，他们的用户中有61％在决定在该公司申请工作之前积极地对公司进行研究。 根据StackOverflow的《开发人员调查》 ，我们只能期望这个数字对于拥有98％就业率(3.9％兼职工作)的专业开发人员来说会更大 。

Developers put your company and products under the microscope when considering an opportunity to work with you. For companies that offer publicly accessible APIs, it’s a portal into the engineering practices in your company (and offers the possibility of discovering major red flags).

在考虑与您合作的机会时，开发人员会将您的公司和产品放在显微镜下。 对于提供可公开访问的API的公司而言，它是进入您公司的工程实践的门户(并提供发现主要危险信号的可能性)。

Seemingly basic things like using the wrong HTTP methods to perform actions on resources, not versioning endpoints, and poor documentation could be all a developer needs to decide if they’ll consider joining your engineering team or move on instead.

看似基本的事情，例如使用错误的HTTP方法对资源执行操作，而不是对端点进行版本控制，以及不良的文档，这些都是开发人员需要决定是否考虑加入您的工程团队或继续前进的全部。

I’m sure you’d agree that losing top talent to the competitor is the last thing any ambitious business would want.

我相信您会同意，将雄心勃勃的人才流失给竞争对手是任何雄心勃勃的企业所希望的最后一件事。

避免不良的UX (Avoiding Bad UX)

The effects of neglecting user experience as it relates to your APIs can be really costly. You make less revenue and rack up huge load on customer support because almost all your users can barely use your service without needing help.

忽略与API相关的用户体验可能会造成巨大的损失。 由于几乎所有用户都不需要帮助，就几乎不能使用您的服务，因此您的收入减少了，并增加了巨大的客户支持负担。

If you’re interested in making the lives of developers that use your products easier, the following steps might help.

如果您有兴趣简化使用产品的开发人员的生活，那么以下步骤可能会有所帮助。

文档是关键 (Documentation Is Key)

The documentation is simply the gateway to your product. It contains detailed instructions on how your API can be used, and you don’t want to get it wrong. It should be complete, well-structured so that information is easy to find, and it must contain examples.

文档只是您产品的门户。 它包含有关如何使用API​​的详细说明，并且您不想弄错它。 它应该完整，结构合理，以便易于查找信息，并且必须包含示例。

Also, all information needed to use your API must be in one place. Your users shouldn’t have to visit different sources just to understand the proper way to call an endpoint.

另外，使用API​​所需的所有信息都必须放在一个地方。 您的用户不必只是为了了解调用端点的正确方法而访问其他资源。

You should especially avoid sharing API documentation in pdf formats. It introduces more problems than it solves, and you don’t want to get support tickets because the user is trying to consume your API using an obsolete document as a guide.

您尤其应该避免以pdf格式共享API文档。 它带来的问题比解决的问题多，并且您不想获得支持票，因为用户正试图使用​​过时的文档作为指南来使用您的API。

There are tools available online that allow users to visualize and consume endpoints. It is advisable to leverage these tools for creating and maintaining robust API documentations.

在线上有可用工具，允许用户可视化和使用端点。 建议利用这些工具来创建和维护可靠的API文档。

拥抱标准做法 (Embrace Standard Practices)

You’re trying to sell a product. The aim is to attract as many customers as you can while eliminating barriers that might prevent users from using your product.

您正在尝试销售产品。 目的是吸引尽可能多的客户，同时消除可能阻止用户使用您的产品的障碍。

When you’re trying to get as many developers as possible to use your API, you have no business shipping your own API development standards or patterns. Huge companies with a large customer base can afford to perform this sort of experiment, but even then the results are usually not favorable.

当您试图吸引尽可能多的开发人员使用您的API时，您将无须交付自己的API开发标准或模式。 拥有大量客户群的大型公司可以负担得起此类实验的费用，但即便如此，结果通常也不令人满意。

Version your APIs, use correct HTTP methods to perform actions on resources, ensure that your response is well-structured, and return correct status codes depending on the success or failure of a request.

对API进行版本控制，使用正确的HTTP方法对资源执行操作，确保响应的结构合理，并根据请求的成功或失败返回正确的状态代码。

The OpenAPI is one widely accepted spec for designing REST APIs. It is backed by Microsoft, Google, and many other leaders in the tech space.

OpenAPI是用于设计REST API的一种广泛接受的规范。 它得到了Microsoft，Google和技术领域许多其他领导者的支持。

An even better approach would be to conduct a study or send out surveys to developers that represent your target market. Try to find out which of these specs they adhere to and attempt to tailor your APIs to those.

更好的方法是进行研究或向代表您目标市场的开发商发送调查。 尝试找出它们遵循哪些规范，并尝试针对这些规范定制您的API。

Developers are less likely to adopt unfamiliar technologies when there are more familiar alternatives. You definitely don’t want to give them any excuse to not use the product you’re offering.

当有更多熟悉的替代方法时，开发人员不太可能采用不熟悉的技术。 您绝对不想给他们任何不使用您所提供产品的借口。

超主动支持渠道 (Ultra-Active Support Channels)

Having several dedicated support channels for handling customer complaints and requests for help is highly important. Software developers want to get swift solutions to blockers they might encounter while consuming your APIs, making response time of utmost importance.

拥有几个专门的支持渠道来处理客户的投诉和帮助请求非常重要。 软件开发人员希望获得使用他们的API时遇到的阻止程序的快速解决方案，从而使响应时间变得至关重要。

Companies have started moving on from e-mail as the default means of providing support to users because it is just too slow. And, asking developers to send code snippets back and forth through e-mail is one of the best ways to get them to abandon your product.

公司已经开始将电子邮件作为向用户提供支持的默认方式，因为它太慢了。 而且，要求开发人员通过电子邮件来回发送代码段是使它们放弃您的产品的最佳方法之一。

Flutterwave and Twitter have dedicated forums for promptly attending to issues consumers might have with using their products. Paystack also has a dedicated Slack group to help out users with issues they might encounter while trying to consume their APIs.

Flutterwave和Twitter拥有专门的论坛，可以Swift关注消费者在使用其产品时可能遇到的问题。 Paystack还有一个专门的Slack组，可以帮助用户解决在尝试使用其API时可能遇到的问题。

Using real-time communication channels to handle customer support issues is not debatable. Your users are software developers, and it is essential that they get help quickly.

使用实时通信渠道来处理客户支持问题是不可争议的。 您的用户是软件开发人员，因此必须快速获得帮助。

Also, making sure code snippets can easily be shared through whatever medium you chose to handle customer support requests will earn you bonus points from your users.

另外，确保代码片段可以轻松地通过您选择用来处理客户支持请求的任何媒体进行共享，这将为您的用户赢得积分。

通信 (Communicate)

A tiny change in your request/response formats can cause considerable damage to your user’s product(s) and entire business. It is very important that you let your users know about planned changes, and provide enough time for them to prepare for these changes. As long as you’re sharing useful and relevant information, your users shouldn’t have cause to complain.

您的请求/响应格式的微小变化可能会严重损害用户的产品和整个业务。 让用户知道计划的更改，并为其提供足够的时间来准备这些更改，这一点非常重要。 只要您共享有用和相关的信息，您的用户就没有理由抱怨。

Send emails and follow up emails reminding your customers of that endpoint you’ll be shelving in the coming months. Inform them promptly about security concerns and let them know what to do to be safe.

发送电子邮件和跟进电子邮件，以提醒您的客户该端点将在未来几个月内搁置。 及时通知他们有关安全性的问题，并让他们知道如何安全。

Let your customers know when they’re using old versions of your product and encourage them to upgrade. Making users aware of the improvements you’ve made is a great way to motivate them to consider an upgrade. Most times, your users just want to be assured that the upgrade contains changes they need.

让客户知道他们何时使用产品的旧版本，并鼓励他们进行升级。 使用户了解您所进行的改进是激励他们考虑升级的好方法。 大多数情况下，您的用户只是希望确保升级包含他们所需的更改。

Every consumer that decides to use your API is doing so because they have a reasonable level of trust in your product’s offering. It is only fair that you repay this trust by effectively communicating with them regarding the state of your product and how best they think you can improve your product in order to serve them better.

每个决定使用您的API的消费者之所以这样做，是因为他们对您所提供产品的信任程度合理。 公平地说，您可以通过与他们就产品的状态以及他们认为您可以如何改进产品以更好地为他们提供更好的服务进行有效的沟通来偿还这种信任。

结论 (Conclusion)

Product development is hard. Even more so when you’re in the business of creating APIs that will be consumed by software developers.

产品开发很难。 当您从事创建将由软件开发人员使用的API的业务时，尤其如此。

That said, it is not impossible to create APIs that developers will love to use. It just takes a lot of conscious effort, and I hope these steps will help you in creating web services we’d all love to use.

也就是说，创建开发人员喜欢使用的API并非没有可能。 只需付出很多有意识的努力，我希望这些步骤将有助于您创建我们都喜欢使用的Web服务。

If you have questions or contributions regarding other steps that might help developers enjoy working with our APIs, kindly leave a comment. I’d be happy to read and respond to them.

如果您对其他可能有助于开发人员享受使用我们的API的操作的步骤有疑问或意见，请发表评论。 我很高兴阅读并回复他们。

翻译自: https://www.freecodecamp.org/news/how-ignoring-ux-hurts-your-api-and-what-to-do-about-it-e4f600f9cbfa/

ux可以去哪些公司