I have a mobile app made in React Native, and I've just run into a best practice dilemma i've encountered many times while using Redux/Redux Saga. I would love if i could get someone else's thoughts on this.

For a new piece of functionality i'm implementing, i need to be able to tell how many times the app has been launched. This involves asynchronously retrieving how many times the app was previously launched from the device storage. If there's a new launch happening, i also need to add +1 to the number and store that in the device storage.

This is how i currently do it:

Dispatch appLaunched() action when app launches. Redux Saga takes event. Inside Saga: Retrieve how many times app was previously launched (appLaunchCount) from device storage (wait for async to finish). Add +1 to previous appLaunchCount. Store new appLaunchCount in device storage (wait for async to finish). Dispatch put() with new appLaunchCount to reducer. Update state with new appLaunchCount inside reducer.

My problem with this method is step 6. Technically any part of my app could dispatch a new app launch count to my reducer, with any integer, and the reducer would update the state just the same even though it didn't come from the saga.

My question is this: How can i protect my Reducers/Sagas/Actions so that only my saga can dispatch the action with the current appLaunchCount ?

P.S The only solution i can think of is writing my saga and reducer in the same file, and use private actions that only the saga and reducer can access. I would really hate to have to keep all that code together though.