In this layer, you’ll be able to define packages containing code and types that are at the very base level of your application. “I see Foundation packages on the first layer.” Let’s dive into the different layers of that architecture and the relationships between them. This is a chart of the current package architecture we use at Dashlane. It’s always a good idea to evaluate your options and make the decision that works best for your specific use case. Every team and project is different, and what works for one may not work for others, even though it’s a pretty generic solution. Everyone is free to adapt and improve it per their project’s requirements and needs. It’s important to remember that the architecture I’m illustrating is just a suggestion. In this post, I will present the package architecture we have at Dashlane and explain why it completely fits our needs.

Instead, let’s talk about how to actually separate your code into packages, what packages you’ll have to create, and how to organize them. I won’t be explaining Swift packages, how to create a package, or how to link it because you can find this information pretty much everywhere, including in the official documentation. Using Swift Package Manager, you can modularize your code very easily, and everything is also integrated into Xcode.

If you want proper code organization for your iOS or macOS app in 2023, consider Swift packages: reusable components of Swift, Objective-C, Objective-C++, C, or C++ code.

Dashlane authenticator