小程序无缝滚动_一种无缝收集应用程序审查的方式

小程序无缝滚动

Nowadays app review plays vital role in dictating the success of the company behind. Got overall rating below three then you are done. But how about not getting any rating at all? That’s also the sure way to destruction.

如今，应用程序审查在决定背后公司的成功方面起着至关重要的作用。 总体评级低于三分就可以了。 但是，根本不获得任何评级怎么办？ 这也是销毁的肯定方法。

So what are we going to do here is to ask for review in the right moment as possible when the user seems satisfied with our apps experiences. The right moment comings in, our apps launch the popup screen that ask for review, then.. the user declined, and we lost the opportunity to get good rating.

因此，当用户对我们的应用程序体验感到满意时，我们将在适当的时候要求进行审查。 恰逢其时，我们的应用程序启动了弹出屏幕要求进行审查，然后..用户拒绝了，我们失去了获得良好评分的机会。

But why the user declined? One of the reasonable factor is because he/she knows that he/she has to leave the apps to go to PlayStore just to give rating, then go back to apps, and this seems cumbersome and frustrating!

但是，为什么用户拒绝了？ 合理的因素之一是因为他/她知道他/她必须离开应用程序进入PlayStore才能给出评分，然后再返回到应用程序，这看起来既麻烦又令人沮丧！

Fortunately, now we have In App Review that could be a great solution to provide seamless user experience whenever we want to ask for rating to our user base.

幸运的是，现在我们拥有In App Review，这可能是一个出色的解决方案，可以在我们希望对用户群进行评级时提供无缝的用户体验。

流 (The Flow)

In App Review which come from google play core library, has built-in functionality to launch bottom sheet that contains inquiry dialog to gather rating and review directly from users, without leaving the apps. This seamless experience of review gathering flow may provide lots of advantage to the apps implementing it, that users are more likely to give good rating because it shows on the right moment, and with minimal effort for users to actually provide honest rating and review.

在来自Google Play核心库的App Review中，具有内置功能来启动底部工作表，其中包含查询对话框，可直接从用户那里收集评分和评论，而无需离开应用程序。 这种无缝的评论收集流程体验可以为实施该应用程序的应用程序提供很多优势，因为它在正确的时刻显示，因此用户更有可能给出良好的评分，而用户实际上只需付出最少的努力即可提供真实的评分和评论。

Here is what the result looks like on PlayStore:

这是PlayStore上的结果：

代码 (The Code)

Basically, the implementation is pretty simple. First of all, make sure you have updated your gradle play-core dependencies to latest version:

基本上，实现非常简单。 首先，请确保已将gradle播放核心依赖项更新为最新版本：

implementation “com.google.android.play:core:${playCoreVersion}”// For Kotlin users only
implementation "com.google.android.play:core-ktx:${playCoreVersion}"

Then create ReviewManager instance using ReviewManagerFactory provided from PlayCore library.

然后创建一个使用从PlayCore库提供ReviewManagerFactory ReviewManager实例。

val reviewManager = ReviewManagerFactory.create(activity)

Now you could use ReviewManager that has two main functionalities:

现在，您可以使用具有两个主要功能的ReviewManager ：

1. requestReviewFlow: to request ReviewFlow that may resulting in success or failed if there is any problem

   requestReviewFlow ：请求ReviewFlow，如果有任何问题，它可能会导致成功或失败

2. launchReviewFlow: to launch the review dialog when the request for ReviewFlow return success

   launchReviewFlow ：在对ReviewFlow的请求成功返回时启动审阅对话框

So we request for the flow using this code before actually launch it:

因此，在实际启动之前，我们使用以下代码请求流程：

reviewManager.requestReviewFlow().addOnCompleteListener { request ->
    if (request.isSuccessful()) {
        //launch in-app review flow
    } else {
        //continue app with normal flow regardless of the result
    }
}

then we launch the flow when the returned status is successful:

然后，当返回状态成功时，我们启动流程：

reviewManager.launchReviewFlow(activity, request.getResult()).addOnCompleteListener {
    // The flow has finished,
    // that could mean that it was launched or not,
    // or that the user reviewed or not, 
    // the API does not forward that.
    // Thus no matter the result we continue our app flow
}

For simplicity and reusability, we extract those code into a helper class that called ReviewHelper

为了简单和可重用，我们将这些代码提取到一个名为ReviewHelper的帮助器类中。

object ReviewHelper {  @JvmOverloads
  @JvmStatic
  fun launchInAppReview(activity: Activity, 
                        callback: Callback? = null) {        
    val reviewManager = ReviewManagerFactory.create(activity)
    reviewManager.requestReviewFlow()
       .addOnCompleteListener { request ->
          if (request.isSuccessful()) {                
             reviewManager
               .launchReviewFlow(activity, request.getResult())
               .addOnCompleteListener {                                        
                  callback?.onCompleted()
               }
          } else {
             callback?.onCompleted()
          }
      }        
  }  interface Callback {
     fun onCompleted()
  }
}

so when we want to trigger in-app review from any Activity, we could simply just call:

因此，当我们想从任何活动中触发应用内审核时，我们可以简单地调用：

ReviewHelper
     .launchInAppReview(this, object: ReviewHelper.Callback {
          override fun onCompleted() {
              //review flow finished, resume app flow
          }
      })

Then voila! The in-app review dialog will be shown and interact with user by itself without any special handling from us (and should not, to ensure objectivity of the review).

然后瞧！ 应用内评论对话框将显示出来，并自行与用户互动，而无需我们进行任何特殊处理(并且不应确保评论的客观性)。

指引 (The Guidelines)

• For best practice, we should trigger in-app review when users have experienced the app / game enough so they can provide useful feedback (i.e. when user has successfully completed transaction of mobile data recharge through our apps).
  作为最佳实践，我们应该在用户足够体验应用程序/游戏时触发应用程序内审阅，以便他们可以提供有用的反馈(即，当用户通过我们的应用程序成功完成移动数据充值交易时)。
• We should not overly trigger the prompt to minimize user frustration and limit the usage. For info, Play enforces a quota on how often a user can be shown the review dialog.
  我们不应过度触发提示，以最大程度地减少用户的挫败感并限制使用。 要获得信息，Play会强制设置配额，以允许用户查看评论对话框的频率。
• We should not have manual button to trigger in-app review manually, as the quota is stricted.
  由于配额受到限制，我们不应该具有手动按钮来手动触发应用内审核。
• We should surface the card as-is, without tampering or modifying the existing design in any way — including size, opacity, shape, etc.
  我们应该按原样显示卡，而不会以任何方式篡改或修改现有设计，包括大小，不透明度，形状等。

结论 (Conclusion)

in-app review provides better flow and user experiences for apps to gather reviews and ratings from their user base. Still, there are some guidelines to be followed — some strict and some don’t — to avoid misuse and even worse UX of the apps as a result of not implementing it correctly. Like old saying “With greater power comes greater responsibility”, we should use this brand new feature wisely.

应用内评论可为应用提供更好的流程和用户体验，以便从用户群中收集评论和评分。 尽管如此，仍需遵循一些准则-一些严格的准则和不遵循的准则-以避免由于未正确实施应用程序而导致误用甚至更糟的用户体验。 就像俗语“能力越强，责任越大”，我们应该明智地使用这一全新功能。

Welcome to the new era of apps review! :)

欢迎来到应用审查的新时代！ :)

翻译自: https://medium.com/tokopedia-engineering/a-seamless-way-to-gather-app-review-7b290e7cc29b

小程序无缝滚动