React is syntactic sugar around standard JS functions. Is the same as Component({propOne: propOne, propTwo: propTwo}) So when you say props.propOne in your child component, you get the value associated with that key in the props object. More on reddit.com

IMO inline is harder to read. When using an explicit type or interface you have the props type declared separately and explicitly, which allows for e.g. reusing prop types or compositing types More on reddit.com

It's basically a way to have children with data from the component passed to it. Here's an example without using the technique: const Counter = ({ count, setCount, children }) => ( <> setCount(count - 1)}>- { count } setCount(count + 1)}>+ { children } ) const Result = ({ total }) =>

The total is { total }

const App = () => { const [ count, setCount ] = useState(0) return ( ) } Here we have the state in App because it's needed in multiple different child components. We use children so Result will be rendered when nested within Counter. const Counter = ({ render }) => { const [ count, setCount ] = useState(0) return ( <> setCount(count - 1)}>- { count } setCount(count + 1)}>+ { render(count) } ) } const Result = ({ total }) =>

The total is { total }

const App = () => ( ( )} /> ) Here we have the state in Counter which helps tie the state to where it's relevant and clears up App from state that is only there due to composition. We use render instead here which effectively works like children but with values passed (count in this case). It's up to you when designing your app which approach is right for the situation. Sometimes you'll want the state to be a level up like in the first example because it's used in a lot of areas there, but sometimes you can contain it within one of the child components and use this render technique to expose that higher up in the tree. Hopefully this helps explain it a little more, let me know if you have any questions! More on reddit.com

For me and my team, props are most often used to build stateless components. In general if we pass data as a prop, we know that some other component is in charge of fetching and preparing the data to be used. Props are especially useful when a component is composed of multiple smaller components. I've heard it called the "container/component" pattern in the React community. The container hooks into the state libraries, as you suggest, but then gives the data as props to the stateless components to render. Without using props, we'd have hooks into state libraries in even the smallest of UI components, drastically increasing the amount of work it takes to test things. Stateless components are amazing, and introducing context/state libraries where they don't need to be is unnecessary overhead. More on reddit.com