22.08.2025 aktualisiert
100 % verfügbar
Mobile Software Engineer, Android Developer, Backend Developer
Den Haag, Niederlande
Weltweit
M.Sc. Computer ScienceSkills
JavaAndroid Application DevelopmentContinuous IntegrationGradleIphone AppsAndroid Debug BridgeSpringbootBackendKotlinAndroid Ui
Android Development, Kotlin, Jetpack Compose, Java, Gradle, Android SDK, Spring boot, CI/CD, Koin, Kotlin Multiplatform
Sprachen
GermanMutterspracheEnglishverhandlungssicherDutchgutSpanishGrundkenntnisse
Projekthistorie
As part of the Eropuit team I developed the Eropuit Android app as well as it's backend and routing engine. The Android app was totally redesigned and a new design system was implemented. This was done in jetpack compose for every old and new screen in the app.
Additionally to the new design, new features were added and a new dynamic home page was implemented. For this I took also part in implementing the backend that serves dynamic content depending on the user interests and app screen. Before this change the Android and iOS apps were getting their content from multiple sources. This was moved to the backend, so that now all the logic to gather and prepare the content is in one place and the apps are more lightweight in their logic.
Another big feature I was working on was the bike and hike routing engine that makes it possible for users to plan their own routes in the Android and iOS app. Therefore a new backend service was created that reads all location information from Open Street Maps and uses this extract information to make it possible to plan routes along the Dutch node network (Knooppunten netwerk). There were multiple challenges to overcome with this task, for example the huge file sizes of the OSM files(>4gb) and their parsing and caching.
Additionally to the new design, new features were added and a new dynamic home page was implemented. For this I took also part in implementing the backend that serves dynamic content depending on the user interests and app screen. Before this change the Android and iOS apps were getting their content from multiple sources. This was moved to the backend, so that now all the logic to gather and prepare the content is in one place and the apps are more lightweight in their logic.
Another big feature I was working on was the bike and hike routing engine that makes it possible for users to plan their own routes in the Android and iOS app. Therefore a new backend service was created that reads all location information from Open Street Maps and uses this extract information to make it possible to plan routes along the Dutch node network (Knooppunten netwerk). There were multiple challenges to overcome with this task, for example the huge file sizes of the OSM files(>4gb) and their parsing and caching.
In my role as an Android Developer at Digidentity, I led the planning and implementation of the Digidentity SDK, ensuring secure connection and use of the Digidentity services. Two different SDKs were developed, while one was designed only to provide functionality without any UI. This was targeted for App developers that wanted to build their own UI and app branding while integrating the Digentity services.
The other SDK was building on the first low level SDK and offered ready made UI screens, that can be customized in different styles and different colors. This was created to give App developers an easier to use and faster to integrate approach. With this two SDKs, now if a developer wants to integrate one of the SDKs they can decide to write their own fully custom UI, or use the ready made customizable one from the UI SDK.
Additionally, I developed the Digidentity Android and partially iOS app with a strong emphasis on security, privacy, and usability. This app was using the both created SDKs and therefore. This gave the advantage of improving the SDKs and seeing them from a "user" perspective, since it was the eat your own dog food approach.
The other SDK was building on the first low level SDK and offered ready made UI screens, that can be customized in different styles and different colors. This was created to give App developers an easier to use and faster to integrate approach. With this two SDKs, now if a developer wants to integrate one of the SDKs they can decide to write their own fully custom UI, or use the ready made customizable one from the UI SDK.
Additionally, I developed the Digidentity Android and partially iOS app with a strong emphasis on security, privacy, and usability. This app was using the both created SDKs and therefore. This gave the advantage of improving the SDKs and seeing them from a "user" perspective, since it was the eat your own dog food approach.