Nedap
Jul 2022 — Present
Around 2022 I had the feeling that it was time for the next chapter in my career. One where I could harden my skills by deep-diving in one company, one product or project. I wanted to grow more towards a lead developer position, mainly focussed on Frontend Development.
I’ve always had an interest in Nedap as a company. It was close to home, my grandpa used to work there too, so it already felt special.
Engagements at Nedap
Frontend Developer · Security Management - AtWork
— Present
I transfered back to the AtWork team to continue working on the access management system.
App + Frontend Developer · Security Management - Mobile Access
—
Our job was to provision card credentials on an Apple Wallet, so users could get access to the buildings using their phone and/or Apple Watch. Mobile Access was an extension built on top of the access management system AtWork or AEOS. I built the iOS app that, after authenticating first, showed the credential which was ready to provision and built the flow to add it to the wallet. This was the first time for our department to build a mobile app. I also created an XCFramework, essentially a SDK, for clients to add the functionality to their own app.
To aid nedap in managing companies who had access to the mobile access features, I built an admin dashboard using Angular. Next to the standard company management functionality, I built a custom card designer (to Apple’s guidelines) which was used to create and upload assets to Apple’s Business portal - this determined the look of the provisioned passes.
Responsibilities
- Create and maintain the iOS SDK
- Create, maintain and distribute the iOS app
- Create and maintain the admin dashboard
Achievements
- Implemented and rolled out the mobile access
Frontend Developer · Security Management - AtWork
—
Together with a small team, I was building an access management system for multi-tenant companies. I was responsible for the Frontend Application, written in Angular, and a mock backend (in NestJs).
To support the development, we built a custom component library with our own design system in css. The application was built on top op that, favouring component composition over prop-drilling1. My take on the architecture was that is was too complex, so I opted for a more simplified version, using cleary separated boundaries and oversaw the refactoring.
I also built the CI/CD workflow using GitHub Actions, making sure the testing and building strategies were efficient and improved the dockerfiles using layer caching.
Responsibilities
- Implement the Frontend Application
- Manage the custom component library
- Build and improve CI/CD workflow
Achievements
- Improved the architecture by splitting domains and setting boundaries
Footnotes
-
Passing all properties down to sub-components in the hierarchy ↩