Over the last few years the idea of creating front-end applications implementing the microfrontends design approach became increasingly popular. Not surprisingly - developing the application in a modular way empowers the teams to work with their own pace and take more ownership of the code they write. It can also significantly speed up the delivery of features across the project, as long as it is implemented well. In the very beginning a lot of React Native projects started off as monolithic apps. Even now, when looking for a starter template for a React Native application, it is likely to come across the examples that suggest dividing the code based on its type - screens, components, hooks, helpers, utils, etc. A division that is perfectly suitable for small projects, but in the long run will not be able to guarantee the scalability of fast-growing ones. One that might result in difficult to detect cyclic dependencies, can delay the release of the product due to a simple defect in one of the packages or forces all the teams to use the same tools and boilerplates. Following the principles of feature driven design can help to take the project one step further, offering the possibility to scale it based on - as the name suggests - the development of the features included in it. Not necessarily features commonly understood in the context of the agile methodology, but the product features - the ones that describe the characteristics of what a particular area in the product (and correspondingly in the codebase) is responsible for.