From d436efc46a675a320af13cdc86d072bfade2ea79 Mon Sep 17 00:00:00 2001 From: Website Deployment Script Date: Fri, 21 Oct 2016 16:39:49 +0000 Subject: [PATCH] Updated docs for next --- releases/next/docs/performance.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/releases/next/docs/performance.html b/releases/next/docs/performance.html index 7c1556cfed0..4a0372e8b8b 100644 --- a/releases/next/docs/performance.html +++ b/releases/next/docs/performance.html @@ -19,7 +19,7 @@ generate the static image (frame) that the user will see on the screen for that interval. If you are unable to do the work necessary to generate that frame within the allotted 16.67ms, then you will "drop a frame" and the UI will appear unresponsive.

Now to confuse the matter a little bit, open up the developer menu in -your app and toggle Show FPS Monitor. You will notice that there are +your app and toggle Show Perf Monitor. You will notice that there are two different frame rates.

JavaScript frame rate #

For most React Native applications, your business logic will run on the JavaScript thread. This is where your React application lives, API calls are made, touch events are processed, etc... Updates to native-backed