Start using Binding instead of using findViewByID

The findViewById method is often used in the application to retrieve a view from a view hierarchy based on an identifier but the problem is that this seemingly harmless method can, in fact, cause performance issues in your Android application if used carelessly, as it is a very demanding method in terms of resource usage.

To solve this problem it is possible to make use of view binding, this is a feature that allows you to more easily write code that interacts with views. Once view linking is enabled in a module, a link class is generated for each XML layout file present in that module. An instance of a link class contains direct references to all views that have an ID in the corresponding layout.

An example of a method in which many are made is the getView method located in the following path owncloudApp/src/main/java/com/owncloud/android/ui/adapter/AccountListAdapter.java
in this method calls are made to the findViewById method 7 times which is evidenced in the code snippet below.

TASKS

• Investigate the different view binding libraries to find the implementation that best suits the project architecture. ex https://developer.android.com/topic/libraries/view-binding
• Create branch name binding Transition
• Development tasks
  • Identify classes where there is excessive use of the findViewByID method.
  • Implement view binding on the files identified in the previous step
• Code review and apply changes requested
• Design test plan
• QA
• Merge branch feature/feature_name into master

Start by reading owncloudApp/src/main/java/com/owncloud/android/ui/adapter/AccountListAdapter.java, especially getView and its seven findViewById calls. Then investigate the project's architecture and candidate view-binding libraries, identify the affected classes, and define completion around migrating those classes with an agreed test and QA plan.