-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Kotlin Multiplatform support #46
Comments
Hi! @scottkruse. We do not have any current plans to support kotlin multi-platform in the near future. This could change if we get more customer demand for this feature. In order to understand the scope more, which platforms are you planning to work with? |
Android, Native, JS targets |
I would also like to have this, but mainly for: Android & Native(iOS) |
@scottkruse - I have created a KMP wrapper which should work for you. |
If this could support Android and Native (iOS) also, so mainly the KMM approach, that would be fantastic! |
+1 for this. |
+1 here too, we'd be interested in this. |
Joining in on this - Android and iOS would be great. Actually got here while looking for such library for segment |
@yosi199 - I am using the library I posted above, it's in production. |
Cant get it to compile. getting this: Could not determine the dependencies of task ':analytica:transformAppleMainCInteropDependenciesMetadataForIde'.
Possible solution:
|
Can you post this on the project and not here as it's an unofficial library |
We have created a custom wrapper similar to https://github.com/MyUNiDAYS/Segmenkt and we integrate segment on the android and iOS side only |
I'd like this as well |
Is your feature request related to a problem? Please describe.
Is there plans for enabling Kotlin for multiplatform support? One current pain point is standardizing data flow coming from client apps. Looking at the source it looks well equipped for a Multiplatform future (pure Kotlin, coroutines, kotlinx serialization, etc)
Describe the solution you'd like
Id like to share higher level architecture for data schemas / middlewares between clients.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: