Fork me on GitHub

hi guys is there any good example of code sharing between react native and react web application ( even better if it's in om next 😄 ) ?


@mfikes: thanks ! 😄


@alwx: good article , very informative


@seantempesta: I have the same error when enabling debugging with re-natal, did you find a way to get rid of it ?


(I use re-natal 0.2.19)


@gphilipp: the devtools one?


or what do you mean


When I enable chrome debugging in the native app.


what’s the error you get / mean?


@artemyarulin: yeah I just check it out. I'm still a bit worried that mobile alone is a beast to development with all the catches and fixes to make it work alone for ios and android. I'm considering separate web and mobile development, what is your opinion on this ?


I would say - share library code for fetching ressources and communicating to your server but don’t re-use visual components


both platforms (or all 3 platforms?) have a very different visual feel. A iOS user will throw things at you when the app feels and looks like android


It depends on your app and your interest in investing bunch of time at the beginning in tools and development process. It’s true what @dvcrn said, but at the same time think about login control for example - is there that much of a difference? About your app custom controls, like user avatar with title at the bottom, is there any difference at the end? It’s possible and if you are targeting all the platforms in a feature it may be a good idea to invest some time in that. Although it’s hard and time consuming (I’ve spend 2 month already on it and didn’t wrote any actual line of code yet :))


running tests for example on ios, andorid, web, ui tests, integration test, building CI. Unified way of building staff, devcards like for ios (because it’s awesome), and so on. There are many things actually which takes time but couldn’t be skipped as app would be complex interaction of many tools/languages/libs


I’m going with the approach that I have a shared set of functionality - mostly everything that goes on behind the scenes and take time to create a distinct UI for each platform. Then I tell cljsbuild / shadow-build to compile the library with each of the platforms and generate multiple targets For re-frame for example, all handlers and subs are shared. Just the frontend components are separate


Yep, this is one solution


Is re-natal working for anyone else right now?


I tried it last night, ended up falling back to standard natal


@mj_langford: Did you have any errors?


re-natal itself didn’t throw errors, but the Xcode project wouldn’t run as main.js wasn’t found


several attempts at cleaning and reinstalling, etc, didn’t seem to leave the default skeleton in a state where it would run the simulator


Is om the library most Cljs+RN folks are using?


@mj_langford: interesting, can you describe how to reproduce? What versions do you use?


That was latest on github, and latest published Xcode


I’ll retry and document a repro on the re-natal project today/tonight


@gphilipp: didn't find a fix for the error. I was just hitting escape to clear it, but now I'm frustrated enough I think I'm going to try and build up from the figwheel-react-native template. I'm clearly missing something here. Man the tooling is a mess. I've been trying for over a week now to have a stable om-next environment that is simple.


No offense @artemyarulin. But I am horribly confused by all of the ktoa stuff. It's tough enough to wrap your mind around om-next without the other abstractions. :)


@seantempesta: Have you tried boot-react-native yet? — very different approach than natal/re-natal


@donmullen: no I haven't. I'm not familiar with boot and the readme seemed to assume knowledge of boot to use it.


But I'll give it a shot! :)


@seantempesta: true - boot is worth learning (yet another thing to add to your list!)


Lots of great support over in #C053K90BR


Ah the never ending list. :)


@seantempesta: Yep, could be - ktoa it raw staff and not polished. Have you tried om-next template?