An Opensourced Recipe for Intializing Redux x Android Native Apps

For syncing project structure and frameworks, a case for using Redux

As a software development agency, Oursky handles many simultaneous projects that include mobile and web apps, code diagnostics, and research projects to name a few. In order to allow team members to initialize or switch projects efficiently, the team uses the Redux framework for web apps. However the multiple states problem not only happens on web platforms, but is also common in apps. That’s why we also extended the Redux pattern to platforms such as iOS and Android and built an Android skeleton for our internal use.

There are boilerplates for Redux Web projects, but when it comes to Android, it’s less trivial. That’s why we created an in-house standard template for Android apps that also comes with a simple NodeJS backend minimal set up with Docker.

Disclaimer: Not all Oursky engineers agree with the Redux pattern. Some may use VIPER, MVVC, MVC. Still, Redux is great for syncing a single project across different platforms.

Backend-nodejs

Your turn! How did you use this in your project?

For the Android skeletons, you can copy and use the whole project in skeleton/android-java or skeleton/android-kotlin , and modify the app name, manifest and build configuration to your new app. Don’t forget to rename the package name (it comes with com.oursky.skeleton) to your own as well.

There are also many great things to be included in the standard kit, such as Buddybuild or Travis CI for Continuous Integration. Do you have any must-have starter libraries? Let us know – or send us a Pull Request directly!