ChristianFilipina Mobile App

Architecture

The driving goal of the architecture of the boilerplate is separation of concerns. Namely:

• Presentational components are separated from containers (aka "screens").

  Presentational components are small components that are concerned with how things look. Containers usually define whole application screens and are concerned with how things work: they include presentational components and wire everything together.

  If you are interested you can read more about it here.

• State is managed using global Redux stores.

  When applications grow, sharing state and its changes can become very hard. Questions like "How can I access this data?" or "When did this change?" are common, just like passing data around components just to be able to use it in nested components.

  With Redux, state is shared using global stores, and changes are predictable: actions are applied by reducers to the state. While the pattern can be a bit much for small projects, the clear separation of responsibilities and predictability helps with bigger applications.

  If you are interested you can read more about it here.

• Application side-effects (API calls, etc.) are separated from UI and state manipulation using Redux Saga.

  Using Redux Saga has two benefits: keeping application side-effects and related business logic out of UI components, as well as executing that logic in an asynchronous way without ending in callback hell.

  Sagas are triggered by Redux actions and can also trigger Redux actions to alter state. By using JavaScript generators (yield), sagas are written in a synchronous-like manner while still executing asynchronously.

Content

This project contains:

• a React Native (v0.59.9) application (in "ejected" mode to allow using dependencies that rely on native code)
• a clear directory layout to provide a base architecture for your application
• Redux (v4.0.1) to help manage state
• Redux Persist (v5.10.0) to persist the Redux state
• Redux Sagas (v1.0.2) to separate side-effects and logic from state and UI logic
• React Navigation (v3.6.0) with a NavigationService to handle routing and navigation in the app, with a splash screen setup by default
• reduxsauce (v1.0.1) to facilitate using Redux
• axios to make API calls (v0.19.0)
• prettier and eslint preconfigured for React Native

Directory layout

• App/Components: presentational components
• App/Config: configuration of the application
• App/Containers: container components, i.e. the application's screens
• App/Assets: assets (image, audio files, ...) used by the application
• App/Navigators: react navigation navigators
• App/Sagas: redux sagas
• App/Services: application services, e.g. API clients
• App/Stores: redux actions, reducers and stores
• App/Theme: base styles for the application

Requirements

Node 8 or greater is required. Development for iOS requires a Mac and Xcode 9 or up, and will target iOS 9 and up.

You also need to install the dependencies required by React Native:

• for Android development
• for iOS development

Running the project

Assuming you have all the requirements installed, you can setup and run the project by running:

• yarn install to install the dependencies
• react-native run-android to run the Android application (remember to start a simulator or connect an Android phone)
• react-native run-ios to run the iOS application (remember to start a simulator or connect an iPhone phone)

Useful documentation

Deployment

• Using Fastlane to automate builds and store deployments (iOS and Android)
  • Distributing beta builds

Package dependencies

• You may want to use CocoaPods to manage your dependencies (iOS only)
  • Using CocoaPods to manage your package dependencies

License

This project is released under the MIT License.