cljsrn

https://github.com/drapanjanas/re-natal | https://github.com/drapanjanas/re-natal/wiki/FAQ | https://github.com/condense/mercury-app/wiki | https://github.com/seantempesta/expo-cljs-template/ https://www.npmjs.com/package/create-expo-cljs-app
mdallastella 2020-05-16T17:20:13.139700Z

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...

đź‘Ť 1
lepistane 2020-05-17T17:11:57.140300Z

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.

jgood 2020-05-17T20:55:23.140800Z

React native paper

mdallastella 2020-05-17T22:27:40.141100Z

Thanks guys

Oliver George 2020-05-18T06:36:53.141300Z

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.

Oliver George 2020-05-18T06:38:01.141500Z

What does exist is pretty limited in scope/variety compared with the react web offerings

Oliver George 2020-05-18T06:38:12.141700Z

Elements & paper have some good stuff though

Andrew 2020-05-18T14:03:41.144400Z

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.

đź‘Ť 1
mdallastella 2020-05-18T14:17:16.144600Z

I'm trying Paper at the moment. @andrew513 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.

raspasov 2020-05-18T18:59:44.148400Z

@mdallastella I second what @andrew513 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

raspasov 2020-05-18T19:03:22.148600Z

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

raspasov 2020-05-18T19:05:30.148900Z

With just this tutorial, it’s possible to build quite elaborate UIs

đź‘Ť 2
Andrew 2020-05-18T19:10:00.149200Z

@mdallastella 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.

đź‘Ť 2
raspasov 2020-05-18T19:11:36.149600Z

Think of “view” as a “div”

raspasov 2020-05-18T19:12:58.149800Z

Apply CSS, and prosper 🙂 There’s a little bit of trickery around ScrollView, VirtualizedList (not all that much); but apart from that, RN is not all that much different from web-based CSS/styling

mdallastella 2020-05-18T19:22:17.150Z

Ok, guys, you've got me, I'll give barebone react-native a try, thanks. :simple_smile:

🎉 2