apk-parser VS redux

I've forked and updated an old, archived APK-parsing library (here's the original) that I use for one of my spare time apps (here), and made the library public and alive again, here.

2&3. I see. Sadly the Android framework can't parse split APK files. This is why there are some other libraries. Sadly what I consider as the most intuitive, comfortable, and light (apk parser, which I forked here to solve some of its issues) is not being maintained anymore. Do you know of a nice alternative to it?

In that case, why not take some abandoned library and re-publish it, making other people contribute to it? Example is this one which I've forked from here. It's a library to parse APK files without using the Android framework to do so. I used it on my own app (here) as it has advantages over what Android offers. Sadly it's archived and won't be updated anymore.

You don't need Redux or Jotai right away.

As the official documentation states: Redux is a pattern and library for managing and updating global application state. It serves as a centralized store for state that needs to be used across your entire application, with rules ensuring that the state can only be updated in a predictable fashion (without causing side effects or unexpected behaviors).

Redux Documentation

Hmm, that is a good point that `useActionState` accepts a reducer-like function (although I think it's async in this case?).

And yeah, half of Redux's terminology is simply because the existing Flux Architecture libraries from the prior year all used those terms. There were several debates in the issues about whether to name them "actions", "events", or something else, and the conclusion was "let's just stick with the existing Flux terminology":

- https://github.com/reduxjs/redux/issues/891#issuecomment-147...

FWIW, as I've revamped the Redux docs over the years, I have specifically made sure we describe the "actions === events" aspect:

- https://redux.js.org/style-guide/#model-actions-as-events-no...

- https://redux.js.org/tutorials/essentials/part-1-overview-co...

Libraries like Redux or MobX can be used for state management, but it is important to weigh the pros and cons of introducing a centralized state.

Consider using the useReducer hook or a state management library like Redux or Zustand for complex state logic.

Some even go the opposite direction; in the case of Redux, there isn’t a union type to be found despite Redux being a conversion of Elm to JavaScript, and later to TypeScript. The whole point of Unions is ensure you’re Reducers can only do “1 of 3 things”. Instead, you’ll see String constants, or _maybe_ an Enum if you’re lucky. Often it’s dangerous Records used to narrow a domain when a Union should have been used instead.

React and React Native share many core libraries. You can use the same state management libraries like Redux, MobX, and data fetching libraries like Axios or the Fetch API.

Redux Documentation

Redux is a state management library for JavaScript applications that provides a centralized store for managing the state of an app. It follows a predictable state container model where actions are dispatched to trigger state changes, and reducers are used to define how the state transitions in response to those actions. Redux enforces immutability and a unidirectional data flow, which makes debugging easier and state transitions predictable.