Insurance · Brazil · Android
MAG Venda Digital
A digital sales tool for brokers to follow products and proposals.
Insurance · Brazil · Android
MAG Venda Digital
A digital sales tool for brokers to follow products and proposals.
Android engineering on the digital sales product.
Product evolution in Java/Kotlin, offline data with Realm, Gradle flavors, Firebase/Crashlytics, and an Azure pipeline.
Android · Java · Kotlin · Realm · Firebase · Azure · SERPRO API
Authentication and identity verification
The Venda Digital team delivered facial-recognition authentication and identity verification using the SERPRO API available at the time. The post below documents this collective delivery.
View post on LinkedIn
An Android product for insurance sales
MAG Venda Digital is a tool for brokers to follow insurance products and proposals. I worked at MAG / Mongeral Aegon as an Android developer between August 2019 and February 2021, in the context of sales applications. The work involved evolving a product used in daily operations and supporting maintenance and new version releases.
I developed in Kotlin and Java, working on application flows and the capabilities supporting their use. Local data, distribution configuration, error monitoring and integration with the delivery process were all part of that experience. I worked within the product team, contributing to the areas described in this case.
Information available without a connection
One area was enabling offline use with Realm, providing continued access to important information in the application. For a sales tool, keeping data available on the device supports the user's work when connectivity is unavailable. Local persistence formed part of the technical foundation addressing that need.
Working with offline data adds considerations when implementing flows: the interface needs to use the available information and reflect the application's state. This local-storage experience complemented Android development and work on a production product.
Application variants and version delivery
I worked with Gradle flavors for white-label variants. This configuration supports preparing application versions from a shared codebase, with the intended differences for each variant. The work required considering those configurations during development and release preparation.
I also supported Azure CI/CD processes and mobile releases. Delivering a change involved its implementation, building the application and following the released version. This connection between development and publication formed part of my experience on the project.
Maintenance, tests and code organization
I used Firebase and Crashlytics for incident monitoring and application maintenance, and worked on resolving production issues. These tools connected development with errors observed during product use, supporting investigation of application behavior and guiding fixes.
I also gained experience with JUnit tests and dependency injection in an Android project using Dagger 2. Tests provide a way to check code behavior, while dependency injection helps organize relationships with other components. These practices complemented work on local data, integrations and application maintenance.
Recognition for a team delivery
During my time on the Venda Digital team, the team delivered facial-recognition authentication and identity verification using the SERPRO API available at the time. The recognition post reproduced on this page names the team and me. It records a collective product delivery.
I was part of the team responsible for that delivery, but did not personally implement the facial-recognition feature. My project contribution covered the Android areas described above. This context presents both individual work and the recognition received by the team accurately.