diff --git a/docs/AndroidUIPerformance.md b/docs/AndroidUIPerformance.md
index 2cd5b978a..77ed6a333 100644
--- a/docs/AndroidUIPerformance.md
+++ b/docs/AndroidUIPerformance.md
@@ -7,11 +7,13 @@ permalink: docs/android-ui-performance.html
 next: activityindicatorios
 ---
 
-We try our best to deliver buttery-smooth UI performance by default, but sometimes that just isn't possible. The first step for debugging this jank is to answer the fundamental question of where your time is being spent during each 16ms frame. For that, we'll be using a standard Android profiling tool called systrace. But first...
+We try our best to deliver buttery-smooth UI performance by default, but sometimes that just isn't possible. Remember, Android supports 10k+ different phones and is generalized to support software rendering: the framework architecture and need to generalize across many hardware targets unfortunately means you get less for free relative to iOS. But sometimes, there are things you can improve (and many times it's not native code's fault at all!).
+
+The first step for debugging this jank is to answer the fundamental question of where your time is being spent during each 16ms frame. For that, we'll be using a standard Android profiling tool called systrace. But first...
 
 > Make sure that JS dev mode is OFF!
 > 
-> You should see `__DEV__ === false, development-level warning are OFF, performance optimizations are ON` in your application logs.
+> You should see `__DEV__ === false, development-level warning are OFF, performance optimizations are ON` in your application logs (which you can view using `adb logcat`)
 
 ## Profiling with Systrace