Or it could be some utility or analytics helper that every project has.Īn important thing to take in mind is that all the features chosen for sharing must have the possibility to be extracted gradually. if a field is nullable or not) because with a single source of truth there will also be a single point of failure. Or it could be a feature that centralizes the source of truth (e.g. For example, all the boilerplate code (constants, data models, DTOs, etc), that is boring to write and is more error-prone. Where to start from is subjective and it depends on the specific project, but there are some parts that better suit this topic. Then, this “little piece of tech stack” will be served to the existing projects as a library. But KMP is built around the concept of sharing as much non-UI code as possible, and it is possible to start sharing a little piece of tech stack. And making a refactor to achieve this structure can be extremely difficult for time or management constraints. ![]() ![]() However, existing projects most likely don’t have a mono-repo structure.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |