And I don't love it that much either π
And I don't love it that much either π
Who cares. It's usually in just one file. It's fine. And I like the visual clue of nestedness. Today I had a bug because a Provider was rendered too deep in the tree. It was pretty obvious after looking at that beautiful nested doll of a file.
Have you guys enabled it for the native app as well?
Hello React Native community π
At Kindred, we'd like to start sharing code between our Expo and NextJS apps. More than just utils/hooks, but UI as well.
What would be the best way to do so?
- monorepo: turborepo?
- UI styling: Tamagui? NativeWind? bare RNW? something else?
What do y'all recommend?
That's great to hear. So you just rely on plain react-native-web for the CSS part.
What about responsiveness or animations? Anything fancy?
Do you have any resources about the performance issues of Nativewind? Is it slower on web or native or both?
Maybe @marklawlor.bsky.social can chime in too.
I've also used Tamagui at a previous company and had a great time using it. But it was for a b2b type of app so there wasn't a huge emphasis on beautiful design (and more specific custom design) so Tamagui's UI lib worked well. I'd prefer to use something more barebone for the current company.
Thanks Hailey.
Actually I meant Unistyles. I don't think Restyle works on web...
Can anyone on the @bsky.app mobile team (@samuel.bsky.team @hailey.at?) able to talk about the choice of building an ad-hoc styling/theming system instead of using something like Nativewind or Restyle?
Screenshot diffs from Maestro runs?
React Native. Come for the cross-platform, stay for the hot-reload.
That being said. For our use case of Friday night release, would just run a GH action a couple of hours after EAS build/submit to submit the new build for review. That would leave enough time for the build to be uploaded and processed by Apple.
Same for Android.
The ideal would be an option in EAS submit to create a new version in ASC and submit that uploaded build for review. Hardcoded release notes would be enough for our use case.
Would it be easy to wait for a build/submission in a Workflow?
It's definitely technically feasible as ASC offers an API to create new releases and submit them for review.
medium.com/@colonal/app...
I'm pretty sure those are only TF submissions not review. Same as using `eas submit` separately.
Is there a way to automate that?
I see Fastlane has a `submit_for_review` param but I don't think EAS exposes that.
Every afternoon we use EAS to build and submit a new version to TF and PlayStore internal tracks.
On Friday we also manually create a new version in App Store Connect and Play Store and submit the Friday's build for review (and release on Monday).
Is there a way to automate that?
I see Fastlane has a `submit_for_review` param but I don't think EAS uses that.
Has anyone tried to automatically submit their React Native app with @expo.dev for App Store and Play Store review with EAS?
Does someone remember a 3rd party service that's offering faster/bundle-splitting @expo.dev / React Native OTA updates? Or did I dream this?
Oh and add this: `project: ['src/**/*.{ts,tsx}!'],`
We just used it in our RN/Expo app.
Cleaned up so much code π§Ή
Make sure to add **/*.ios.* and **/*.android.* to your ignore list in your knip.config.ts file.
Haha. My take on Svelte would be pretty short. I'm afraid I'm a React maximalist. Mostly because there's no Svelte Native. React is truly write once, run everywhere.
I recommend subscribing to @sebastienlorber.com's newsletter thisweekinreact.com.
This helps me reduce doom scrolling on x and bsky looking for React and React Native news.
β
We're looking for a strong React Native dev at Kindred (livekindred.com).
Base comp is $170K β $220K plus lots of equity in a hyper growth Series B company.
jobs.ashbyhq.com/kindred/91cb...
Let me know if you're interested.
US or Canada only.
#ReactNative #expo
I personally use getpocket.com which probably uses the same article scrapping method.
Or everyone uses 12ft.io (only works with some paywalls, not all of them).
Any visible (or measured) performance improvements?