This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
- # announcements (3)
- # babashka (23)
- # beginners (54)
- # calva (9)
- # cider (8)
- # clj-kondo (18)
- # cljsrn (25)
- # clojure (69)
- # clojure-australia (1)
- # clojure-europe (7)
- # clojure-spec (13)
- # clojure-uk (1)
- # clojurescript (122)
- # conjure (8)
- # cursive (15)
- # defnpodcast (9)
- # deps-new (2)
- # emacs (22)
- # fulcro (10)
- # graalvm (36)
- # luminus (5)
- # meander (5)
- # minimallist (1)
- # observability (6)
- # off-topic (54)
- # reagent (8)
- # reitit (2)
- # releases (1)
- # reveal (25)
- # shadow-cljs (21)
- # tools-deps (50)
- # vrac (1)
- # xtdb (2)
Hello! If re-natal - https://github.com/drapanjanas/re-natal only supports figwheel, does that mean I'll be unable to import in js libraries? 😮
It will work with react native libraries.
That particular project is a bit dated. Figwheel, ShadowCljs and Krell are candidates.
I have to admit I have been struggling quite abit with how/where exactly to start. I tried some of the links above. Got quite far with Expo, only to learn that there's an issue on the latest android app version
This stuff is an order of magnitude messier than a regular clojurescript webapp.
Are you comfortable with react native?
Unfortunately, i have say not really ;x Are there any tips/guides that you recommend? If i try venturing into it again
My advice would be to start without CLJS. Build up screens that way. You can do that in JS or CLJS. There's less friction in pure JS (the interop on some components gets quite annoying from CLJS). The place where CLJS shines for me is in state management (e.g. re-frame providing state and an event loop).
That's only an opinion. Something I've come to over time. Others might disagree.
What is CLJS actually? I was thinking that it should mean clojurecript? :o (you mean +cljs in the template right) doesn't that add clojurescript?
Sorry, by CLJS I mean clojurescript
I think lots of people will have opinions varied opinions about this stuff.
My main advice would be to be systematic about picking up each layer of technology on the frontend.
1. get comfortable with react native to build components
2. think about state management. I have used re-frame for years so I'm probably a bit biased.
Right now I'm exploring breaking up the problem
1. build components (e.g. UX) as stateless react JS components.
2. hook things up into a stateful app
StorybookJS seems a good way to develop the UX components so they are good/polished before moving onto the complexities of building out a stateful app.
Components take a lot of effort to get right. For mobile apps the polish matters - transitions, layouts on different screens...
Working with the somewhat quirky/stateful/opinionated react native components can be irritating from CLJS
I see i see! I've been trying to work with clojure to build something. But so far haven't managed to really do anything yet. The closest I've come is making a simple telegram bot. Part of it stems from the clojure ecosystem being pretty daunting. Think I havent really been approaching the task incrementally