Architecture and Automation: How Development Processes Work at N26
Ever wondered how a different company handles developing new features and maintaining existing ones? How does development processes look like? How do you grow a feature from an idea to a product in the app store? What steps the implementation need to take before being ready for the public release? We did, but we failed to find much information.
In this talk, titled “Architecture and Automation: How Development Processes Work at N26”, Vincent and I share our app architecture and our automation flow with you, to give insight in our mistakes and successes we encountered along the way.
In short, we cover 3 topics:
- Isolation on the code level — we dive into swift, and how we keep our code easy to manage. We take a closer look into the architectural components we use, and the interfaces between them.
- Isolation on the project level — we talk about how we evolved our monolithical app to a more scalable model. We even get to do `Xcode -> New Project` every time we add a new feature to the app. We cover the biggest upsides and downsides of our approach.
- Delivery — we share our delivery pipeline, 3rd party tools we use, and even some open source tools of our own. We demonstrate how to use Bob to automate trivial tasks using a familiar slack interface.
If you want to find out more, the entire talk is available on YouTube:
Interested in joining one of our teams as we grow?
If you’d like to join us on the journey of building the mobile bank the world loves to use, have a look at some of the roles we’re looking for here.
