Android developer

Technical knowledge

Programming language: Java. New functionalities are no longer developed in Java. These must be maintained and changes will also have to be applied.
Programming language: Kotlin. A large part of the app has been converted to Kotlin. In addition, all new functionalities have been developed in Kotlin. Most of the focus is on this.
Data binding & Live data: All new functionalities with MVVM use data binding and jive data to update the UI.

RXJava: This is widely used. Knowledge and experience is actually a must.

Room DB (sqlite): Local caching is done with Room DB. Knowledge about this is a plus, but not required.

Retrofit: Network framework. Knowledge and experience with this is required.

Firebase realtime database: Contract data, promotions, etc. are loaded via Firebase realtime database. Extensive knowledge is not necessary. An experienced developer will handle this.
Development methodology: MVP. This is currently being phased out, but will still need to be maintained. For example, adjustments are still being made, but it is not a method that is further used within the app.
MVVM: All new functionality is implemented through this principle. Several “old” parts have also been converted to this principle.

CI: Bitrise. easy if someone knows about it. Is not a necessity

Testing: Little to no implementation. Made an attempt, but not able to make any progress yet.

Personal / character

The team needs a developer who takes the lead on mobile and acts as a point of contact. Not a passive but proactive developer. Often adjustments and improvements within the app are at the request of the developer and not directly from the customer. There is still legacy in the app. The developer must dare to take the step / realize that converting / rebuilding into a new structure yields more profit than endlessly adapting existing functionality.