Hi guys!
I can't figure out how to represent the overall project architecture, can you help?
I'm going to have the common part (85% of business logic) for both platforms (ios & android for now), with specific rendering (10% of UI) and drivers (5% of network, database, file managing, keychain access, etc).
Also, I use some Cocoapods dependencies for implementing iOS "drivers".
And some of them currently are Swift-only that's not supported by KMP as I've read.
--
So, after two days of thinking, I do imagine the following ways.
But can't understand which of them can be realistic:
1) Somehow link the Cocoapods into KMP:Project to be able access them from KMP:Project side by doing `import cocoapods.somelib`; but this way is just for ObjC-compatible pods; And if all that's possible, then KMP:Project would be entry-point and would simply manage overall app lifecycle on his own by calling platform-specific code via expect/actual.
2) Link the KMP:Project as pod to Xcode:Project as a block of common functionality, thus Xcode:Project would be entry-point, and would hold reference to + perform communicating with KMP:Project, and implementing UI and "drivers"; And, this could allow to link Swift-only pods (?) as they will link straight to Xcode:Project this way.