It would be great to have a completion callback to execute something after the ScrollView has finished scrolling from a scrollTo call.

React Native start to be mature enough to think about adding the ability to place, executed in parallel, some controller's scripts in different threads. The one and only bottle neck of React Native is the slowing performance on view building and animations due to the single Javascript thread. We see appearing here and there different node modules that could be merge into React Native core. I specifically think about: - for the workers: https://github.com/devfd/react-native-workers - Hamster for the multithreading engine: http://www.hamsters.io Starting developing on that direction makes huge changes in the app. If those libs were included in Core, there's maybe a way to start threads transparently by placing specific markers at the head of the JS Classes? React-Native is awesome and have all to be the next cross platform language for web and mobile. But in the near future, when the applications will be complex enough, the criticism will rapidly comes from the lack of speed and smooth transition that make all the difference between an 100% Native App and a 80% Native React-Native App...

I haven't seen any mention on the ability to create Android home screen widgets with react-native. Are there any plans for it? Is this something to be included in core to include or should the community jump on it?

Headless JS is very useful for running background jobs and it would be nice if it worked for iOS as well. It is already supported for Android: https://facebook.github.io/react-native/releases/next/docs/headless-js-android.html

This would increase the flexibility developers have regarding automated scrolling, e.g. a 1,000 item list should not be scrolled to the end at the same speed as a 10 item list does. If you'd like I would add a PR for this feature :)

Here is my ScrollView: <ScrollView ref={ 'scroll' } horizontal={ true } onScroll={ this.onScroll } showsHorizontalScrollIndicator={ false } onTouchStart={ () => console.log( 'touch start' ) } onTouchMove={ () => console.log( 'touch move' ) } onTouchEnd={ () => console.log( 'touch end' ) } onScrollBeginDrag={ () => console.log( 'scroll begin' ) } onScrollEndDrag={ () => console.log( 'scroll end' ) } onMomentumScrollBegin={ () => console.log( 'momentum begin' ) } onMomentumScrollEnd={ () => console.log( 'momentum end' ) } onStartShouldSetResponder={ () => console.log( 'on start' ) } onStartShouldSetResponderCapture={ () => console.log( 'on start capture' ) } onScrollShouldSetResponder={ () => console.log( 'on scroll' ) } onResponderGrant={ () => console.log( 'granted' ) } onResponderTerminationRequest={ () => console.log( 'term req' ) } onResponderTerminate={ () => console.log( 'term' ) } onResponderRelease={ () => console.log( 'release' ) } onResponderReject={ () => console.log( 'reject' ) } onScrollAnimationEnd={ () => console.log( 'anim end' ) } scrollEventThrottle={ 16 } contentContainerStyle={ styles.container }> As it is only touch start, touch move, and occasionally touch end get fired. I really need something like onScrollAnimationEnd which is currently iOS only

Currently iOS has some really handy methods for ScrollView, in my case specifically contentOffset. These are needed in Android for the ScrollView to be as powerful as Native.

On Android, there is TextView's textIsSelectable. On iOS, there is UITextView's selectable. These allow one to click-and-hold to select text in a non-editable text view. It would be nice to expose this feature through React-Native's <Text>

https://github.com/facebook/react-native/issues/167 "I wanted to start a discussion about the timers and an API that exposes the capabilities of the system timers. A couple of things I noticed were that the timers use CADisplayLink on the main thread and also listen to the UIApplication state notifications. To my knowledge this works well for timers that are coupled to the UI (requestAnimationFrame comes to mind, there may be other uses). I'd like to discuss timers that do other work e.g. interact with the event loop or schedule background tasks, and how they co-interact. Event loop timers seem to fall into two categories - those that run at the end of the current loop and those that run right after. This is like process.nextTick and setImmediate. These aren't too hard to implement though there are a couple of gotchas like warning if a process.nextTick handler endlessly schedules itself before blowing the stack. I would also expect both of these timers to run even if the app is inactive or backgrounded (e.g. say you get a network response while the app is backgrounded and schedule some work to run soon after - it should run in the background). Background task timers (setTimeout, setInterval) raise a couple of questions like the semantics of a zero-ms timeout. I would also propose that these run in the background as well to address the use of running code that does not need the app to be foregrounded. And, if the app is backgrounded there is little harm in running UI code anyway -- in cases where it does matter, the timer handler can check the UIApplication state. Background task timers that repeat are also good candidates for energy optimization. One thing that OS X systems do is coalesce timers where possible, partly aided by the programmer providing a tolerance value. If many running apps schedule timers that can overlap within their respective tolerance windows, the system may wake the CPU just once to run all of those tasks together." - @{ide}

Respected community, I've gone through the issues and found this is yet to be implemented for Android. I'm aware of `elevation` property but this is something iOS has but not Android.