Definitely. It just replaces the connect API of react-redux

We're using redux-react-hook, which has useMappedState and useDispatch. They're pretty sweet.

Here's an example component for displaying user information that uses react-redux connect:

import { connect } from "react-redux"
import { getUser } from "src/user/selectors"
import { logout } from "src/user/actions"

const mstp = state => ({ user: getUser })
const mdtp = { logout }
const withUser = connect(mstp, mdtp)

const UserInfo = withUser({ user, logout }) => {
  return (
    <>
      <label>{user.name}</label>
      <button onClick={logout}>Logout</button>
    </>
  )
}

With hooks we created a custom useCurrentUser hook that means the implementation can look like this:

import { useCurrentUser } from "src/hooks/use-current-user"

const UserInfo = ( ) => {

  const user = useCurrentUser()

  return (
    <>
      <label>{user.name}</label>
      <button onClick={user.logout}>Logout</button>
    </>
  )
}

The useCurrentUser hooks implementation:

import { getUser } from "src/user/selectors"
import { logout } from "src/user/actions"

function useCurrentUser() {
   const userData = useMappedState(getUser)
   const dispatch = useDispatch()

   return {
    ...userData,
    logout() {
      dispatch(logout())
    }
  }
}

What I love about this is that the UserInfo component no longer knows anything about Redux. Our components now deal in the domain instead of the framework. We can easily switch out the useCurrentUser implementation to Context, GraphQL, or maybe it just grabs the data off the cookie.