Spencer Ahrens

Perhaps a new top-level `StyleSheet.createThemed`? ``` const themedStyles = StyleSheet.createThemed({ dark: { ... }, light: { ... }, customTheme: { ... }, shared: { ... }, }); ``` then a...

Another option that would be much more flexible would be to make it functional: ``` const themedStyles = StyleSheet.createThemed((theme: 'light' | 'dark') => ({ container: { flex: 1, backgroundColor: ThemeColors.surfaceBackground[theme],...

Thanks for the clear bug - this is still an issue. Looks like this is because we wrap the `RCTTextInputView` component in a `TouchableWithoutFeedback`. As a workaround, you can use...

@hedgerwang: are you thinking about an animated transition (like a cross-fade) from route C to D since the top of the stack is being replaced? @ericvicenti: I'm not sure how...

Would it be possible to provide a simple hook that people could use to do the transition animation (with some jankiness) that by default does nothing, without increasing the complexity...

Actually, I think you could build any "replace" transition as a push and then a remove after the animation (e.g. a cross-fade) completes - any examples where that wouldn't work?...

What are some reasons you would expect `renderScene` be called more frequently than `renderRoute`?

Yes, using transforms would be much better. @vansonleung: `translateX` should work on Android, but I believe it requires the decomposed form: ``` style={{ transform: [ {translateX: 200}, ], }} ```