We're doing some consulting work at the moment. Advising a large client on a digital transformation project. It's made me look more closely at non-RN mobile app development options more closely. This NuBank article makes a good pitch for the strengths of Flutter. https://building.nubank.com.br/scaling-with-flutter/

Wondering if anyone has switched from Flutter to RN and has viceral reactions to the claims.... "After gathering evidence, the team decided to adopt Flutter, thanks to its excellent testing capabilities, such as built-in testing infrastructure for Unit, Integration, and End-to-End tests without the need for rendering to the screen. Overall, — compared to other options — they also found the Flutter development experience to be superior, with better hot reload capabilities, robust official documentation, and a more stable API."

I’m trying to use the options prop to have a right header button and a custom title, something like the following https://reactnavigation.org/docs/header-buttons/:

function StackScreen() {
  return (
    <Stack.Navigator>
      <Stack.Screen
        name="Home"
        component={HomeScreen}
        options={({ navigation, route }) => ({
          headerTitle: props => <LogoTitle {...props} />,
        })}
      />
    </Stack.Navigator>
  );
}

[:> (.-Screen Stack) {:name "Event Title"
                           :options (fn [navigation]
                                      {:headerTitle (fn [props] "Some Title")
                                       :headerRight
                                       (r/as-element
                                        [button {:title "Next"
                                                 ;;:onPress #(dispatch [:add-thumbnail navigation])
                                                 }])})
                           :component (r/reactify-component event-title)}]

I think you might need to wrap the return value of the function in (clj->js …), @ps

@pez now I have the following:

[:> (.-Screen Stack) {:name "Event Title"
                           :options (fn [navigation]
                                      (clj->js
                                       {:headerTitle (fn [props] "Some Title")
                                       :headerRight
                                       (r/as-element
                                        [button {:title "Next"
                                                 ;;:onPress #(dispatch [:add-thumbnail])
                                                 }])}))
                           :component (r/reactify-component event-title)}]

Wild guess: try with r/as-component

@pez where should I put as-component?

Sorry, instead of r/as-element, I meant.

@pez That gives the following

I’m out of guess, unfortunately. I haven’t used that API myself. (But I’m pretty sure the clj->js is needed there.)