How many production-scale projects don't use Redux? Is this more common than I'm thinking and hearing?
Show HN: Clothes shopping app UI built in React Native
11–20 of 54 posts
Re: Show HN: Clothes shopping app UI built in React Native
#12Re: Show HN: Clothes shopping app UI built in React Native
#13I was surprised to see that this uses React without Redux for state management. I'm aware that Redux is a separate, optional, codebase, but from how people have been talking, it seemed like just about everyone was Redux or bust. How many production-scale projects don't use Redux? Is this more common than I'm thinking and hearing?
Re: Show HN: Clothes shopping app UI built in React Native
#14I was surprised to see that this uses React without Redux for state management. I'm aware that Redux is a separate, optional, codebase, but from how people have been talking, it seemed like just about everyone was Redux or bust. How many production-scale projects don't use Redux? Is this more common than I'm thinking and hearing?
Re: Show HN: Clothes shopping app UI built in React Native
#15I was surprised to see that this uses React without Redux for state management. I'm aware that Redux is a separate, optional, codebase, but from how people have been talking, it seemed like just about everyone was Redux or bust. How many production-scale projects don't use Redux? Is this more common than I'm thinking and hearing?
1. Minimal use of Redux
2. Started with Redux, migrating to eliminating Redux.
This has mainly been due to using other technologies for dealing with API data (i'm using Relay, but there are other options), and having relatively little need for client-side state that can't be handled at the component level. When I have needed simple shared state, I just use the context API. If I absolutely needed a lot of client-side shared state, I might still consider Redux, but would also strongly consider client-side GraphQL extensions (both Relay and Apollo support these) so that everything follows the same patterns.
Re: Show HN: Clothes shopping app UI built in React Native
#16I love exploring structure and approach in codebases written recently, it’s one of the best ways to learn a new language or mentally refresh on what new libraries and tools exist. Anyone know of good resources or proper search terms for “show me fully executed applications built on X language/stack within the past year”
I've found realworld.io is pretty good for working examples of different stacks. Maybe not as up to date as you're looking for, but a good start for new languages and frameworks.
Re: Show HN: Clothes shopping app UI built in React Native
#17I was surprised to see that this uses React without Redux for state management. I'm aware that Redux is a separate, optional, codebase, but from how people have been talking, it seemed like just about everyone was Redux or bust. How many production-scale projects don't use Redux? Is this more common than I'm thinking and hearing?
Re: Show HN: Clothes shopping app UI built in React Native
#18I am wrong to wonder why this doesn't run in a browser, or does it? I was under the impression React uses the browser DOM (or virtual DOM of course) to render its components...wouldn't that mean it can run on the desktop in a browser?
Compare also with Flutter [0], a new competing application development stack from Google with a similar architecture (= components all the way down) and development experience (= live reloads), but which will in production compile everything to native (instead of interpreting JS).
Re: Show HN: Clothes shopping app UI built in React Native
#19I was surprised to see that this uses React without Redux for state management. I'm aware that Redux is a separate, optional, codebase, but from how people have been talking, it seemed like just about everyone was Redux or bust. How many production-scale projects don't use Redux? Is this more common than I'm thinking and hearing?
I assume it was used for some tutorial?!
Not saying you can't get away with not using redux at all but this isn't an example of that. Try mobx or unstated for simple state management.
Personally my projects tend to use it because I'm used to it. Once you get your head around it the boilerplate is not too much to deal with and it slides in so nicely with react. You just need to think in a functional way.
Also features like redux-persist make it powerful. You wouldn't believe the number of apps released on the stores using RN that don't persist state and simply restart when the phone runs out of memory or gets rebooted.
Re: Show HN: Clothes shopping app UI built in React Native
#20I was surprised to see that this uses React without Redux for state management. I'm aware that Redux is a separate, optional, codebase, but from how people have been talking, it seemed like just about everyone was Redux or bust. How many production-scale projects don't use Redux? Is this more common than I'm thinking and hearing?
Every app i've worked on for the last 3 years has fit in one of two categories: 1. Minimal use of Redux 2. Started with Redux, migrating to eliminating Redux. This has mainly been due to using other technologies for dealing with API data (i'm using Relay, but there are other options), and having relatively little need for client-side state that can't be handled at the component level. When I have needed simple shared…