Love the simplicity of cycle.js over redux, but still being new to react native, I am a little worried react native won't be a priority for cycle.js support. What is the plan for integrating with react native?

There should be a react driver..

The rows of a React Native ListView component are not being augmented with event handlers in this driver because renderRow's output is not reachable from the root VTree.

We need to make a CycleListView component that augments rows with event handlers when renderRow is called. See http://facebook.github.io/react-native/docs/listview.html#renderrow

Hi there,

Looking at https://github.com/staltz/manyverse it seems that doing React Native with Cycle.js isn't best done with this module anymore?

Drawing from the code in manyverse, I was able to get things going (including with RN Web and Expo) with only @cycle/react and the following code in App.js of any expo boilerplate:

import { TouchableOpacity, View, Text } from "react-native";
import { h, makeComponent } from "@cycle/react";

const main = function(sources) {
  const inc = Symbol();
  const inc$ = sources.react.select(inc).events("press"); // Press will work in RN and RN Web

  const count$ = inc$.fold(count => count + 1, 0);

  const elem$ = count$.map(i =>
    h(TouchableOpacity, { sel: inc }, [
      h(View, [h(Text, {}, `\n\n\n\nCounter: ${i}`)])
    ])
  );

  return {
    react: elem$
  };
};

const App = makeComponent(main); // makeComponent(main, drivers) is also possible.

export default App; // To make Expo happy.

Do I run React-Native init? Does the example code go in the index.android.js? or in a component? Please help

issue
run doesn't work as expected as nothing is shown on the screen unless a delay is added and setup is used instead of run.

eg:

const prog = setup(main, {
  react: makeReactNativeDriver(appName),
});

setTimeout(() => {
  prog.run()
}, 1);

This was discussed in a PR previously and I finally got time to review the cause.

It's because of the weird implementation of setImmediate on the iOS side of things, which never really works as needed, or to be fair there's no scheduling at all and things execute literally immediately and the contextual wait never really happens.

Which in turn makes it impossible for quicktask to execute the addition of listeners which is done in @cycle/run

A quick fix for this on the user side is to change this in the index.js code right before run()

global.setImmediate = fn => setTimeout(fn, 1);
// or 
// global.queueMicrotask = fn => setTimeout(fn, 1);

run(main, {
  react: makeReactNativeDriver(appName),
});

It's not a graceful solution but I don't think we need to patch quicktask to change it's priority but instead if run could just use timeout, that'd work in all places? except when process is available.

Or if there's a better solution, we could go with that

Just stumbled across this.
https://github.com/gk-brown/MarkupKit
It is iOS only, but imagine the Cycle architecture without JS.

reactNativeDriver() function in the current state is not mounting the app/running the application unless there is an initial emission on the stream to do the mounting of the app.

Is it because of missing createElement to be called on Root?
react-dom driver works fine because root was wrapped with createElement(Root) before mounting to container, while the react-native driver doesn't do it before registering component why?

https://github.com/cyclejs/react-dom/blob/e1e5da8e998854344acdc117278e9c773ffecca3/src/index.ts#L10

André @staltz will it fix the react native app initial mounting problem? I don't know, I would like to learn.

I'm curious, any thoughts on ReactXP, which tries to bridge React Native and React (Web)?

I'm new to Cycle.js.

What would this look like with more scenes?

I love the concept behind cyclejs, but it seems like the docs are out of date as the example is not working with the current RN deps. Also there seems to be few work done on the react-native driver overall.
Do you think this project will get more attention in the future?

Expo expects App function (that returns react native components) to be the default export. This is prevents the usage of makeReactNativeDriver function as usual.

Working with React Native, I find the most terrible thing that you don't have direct control of the keyboard.
It could be cool with a declarative Keyboard driver, where one could attach toolbar elements, etc. It would be hard to handle in pure React Native, since there is really only 'one' driver (the vdom). But Cycle's architecture could handle having a View driver, and a Keyboard driver. Further more it could be cool to have a more purely declarative View driver, something akin to snabdomm for native. Then we can't piggyback on React Native, but I honestly don't find RN declarative enough. I imagine making our own bindings would be quite an undertaking, but it seems the driver architecture of Cycle is much better suited abstraction for native development, especially because there are multiple views (virtual keyboard, vdom). Any input on these ideas?

@staltz
This package seems to be a little bit outdated, outdated version of cycle-react dep, deprecated ListView, etc? You don't use it? Seen you've made https://github.com/staltz/cycle-native-navigation