rootstrap / android-base Goto Github PK

Description

• Add the app permission manager for Activities or Fragments.

In the repository are some files which were auto-generated by Android Studio (or another tool) and sometimes they change based on user configuration or IDE version.

These values and their updates can cause merge conflicts or lead to unexpected errors on some user machines, so to avoid them we need to verify which auto generated files are being tracked in Git and remove them, after that we need to add the corresponding rules into the .gitignore file

Based on the comment by @marcossalto in #51 (comment)

Description

• Primarily update Kotlin and Hilt because they are outdated (and Hilt's version is alpha).
• Secondly update the rest of the dependencies and fix update conflicts to keep the whole project up to date and to avoid doing it by hand in new projects that start from this template.

Description

• We need to add a persistence library like Room or SQLDelight

Objective

• Add unit test and UI test.

Description

• Migrate navigation to use jetpack navigation components.
  Official doc: https://developer.android.com/guide/navigation/navigation-getting-started

Description

• We need to add a dependency injection tool like Dagger, Hilt or using a service locator pattern.

Add explanation on how to configure and use Fastlane

• Adding Coroutines to the networking layer.
• Use coroutines with async task, bitmaps/videos manipulation, Room data base.

Could someone please share your thoughts about why this was implemented this way?

We faced that when we add a new commit to a branch we end up with all the code modified and sometimes the changes that we added are deleted. This can be prevented by adding the flag --no-verify when commiting but it makes no sense to have a tool configured and then avoid using it on purpose.

Other findings were that the steps ktlintFormat and ktkint when excecuted separately doesn't make any modifications to the code, so the issue could be made by the stash commands.

I'd like to open a discuss here about how to improve this

Description

• Secure the Shared pref information.

Description

• Add a signing config for suitable build variants that needs it

Description

• Select which CI tool is more convenient for this project
• Add the selected CI tool 😂

As discussed on the Android's Roundtable of 01/12/2021 it seems good to migrate the current LiveData implementations to Kotlin flows, which is the new official way of sharing reactive information between activities and viewmodels.

It brings many benefits like chaining operations, cold and hot flows, defining when we want to react to changes (for example, if we want to react only when the view is resumed or when it is started), independence from Android (we can use it in MPP projects), etc.

As an additional point new libraries built on kotlin are recommended to use with Flows, an example of it is the Android architecture's Paging Library.

Kotlin flows on Android : https://developer.android.com/kotlin/flow

As discussed on the Android Roundtable of 01/12/2021 there will be very useful to create an application's flow using a single activity structure with a bunch of fragments for each section on the flow, using the Navigation component and SafeArgs plugin to navigate through the flow. And a shared and specifics viewModels with some logic.

The objetive is to have a common way of app's navigation which sohuld be easy to replicate/modify for the specific project's requirements. So every project which starts from this base can have the same standard for navigation.

Navigation: https://developer.android.com/guide/navigation
SafeArgs: https://developer.android.com/guide/navigation/navigation-pass-data