This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-05-16
Channels
- # announcements (7)
- # aws (9)
- # babashka (31)
- # beginners (28)
- # calva (14)
- # clj-kondo (29)
- # cljs-dev (23)
- # cljsrn (16)
- # clojure (21)
- # clojure-france (1)
- # clojure-nl (2)
- # clojure-spec (20)
- # clojure-sweden (4)
- # clojure-uk (6)
- # clojurescript (62)
- # community-development (5)
- # conjure (81)
- # cursive (14)
- # datomic (5)
- # defnpodcast (2)
- # docker (1)
- # figwheel-main (11)
- # fulcro (17)
- # graalvm (5)
- # jobs-discuss (5)
- # kaocha (1)
- # off-topic (54)
- # pathom (1)
- # pedestal (1)
- # quil (1)
- # re-frame (34)
- # shadow-cljs (34)
- # tools-deps (39)
- # uncomplicate (2)
Hi. first mobile app here! I know it's a bit off-topic, but what do you guys use as component library for you react-native apps? React-native builtin components are quite barebone...
any components lib i used https://react-native-elements.github.io/react-native-elements/ a lot it really depends you are trying to achieve and what you want to do.
Thanks guys
Our experience is there's a lot more "roll your own" in the RN landscape. I came in wanting comprehensive libraries but now acknowledge that building things up isn't really all that bad.
What does exist is pretty limited in scope/variety compared with the react web offerings
Elements & paper have some good stuff though
I've found that component libraries almost always aren't worth the trouble. It inevitably ends up that you can't do what you want to do with them or there are bugs and you end up spending tons of time fighting with the library instead of building your app. Unless you're building a toy/demo app I'd avoid component libraries. The primitives available in react native are quite powerful and easy to use. Once you get accustomed to them you can build pretty much anything you need quite quickly.
I'm trying Paper at the moment. @UHDB725UG you're right, a lot of time we end up to write our own stuff instead of using frameworks, but as I said it's our first mobile app and we don't have a lot of time to invest into building from scratch, unfortunately.
@U052TDWT7 I second what @UHDB725UG said; if you have even half-decent understanding of CSS/FlexBox, in just a few days you’ll be way more productive with your own CSS vs. trying to shove a square peg in a round hole via a component library; RN styling is really just old school CSS+flex box
I hadn’t really used flex-box before React Native, I found their guide super helpful and with very good examples https://reactnative.dev/docs/flexbox#__docusaurus
@U052TDWT7 my personal experience is that it actually saves time to use primitives instead of a component library when building something with an unfamiliar technology. Using a component library ends up being a crutch that obscures and prevents you from learning the really valuable foundational knowledge that you will need to gain anyway. You end up coding yourself into a box you don't fully understand which means not being able to realize your vision and having technical debt to clean up. That's not a super fun place to be. Again just my experience, it isn't necessarily that way for everybody in every situation. IMO the primitives in RN appear super barebones at first glance but in practice they're very powerful. You can do a ton with them really quickly once you get the hang of them.