You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
I noticed allot of the "compose" views are just wrapped older XML views with some Compose wrappers, whats the plan to move to native first compose views?
The reason is I want to fork to make a Stripe KMM library, but the lift is basically writing the whole thing as is unless you can move to pure kotlin and compose.
Describe the solution you'd like
Native Compose views vs wrapped XML views.
Describe alternatives you've considered
Writing everything from scratch...
Additional context
With KMM popularity, I wouldn't expect a KMM library (although that would be super nice), but if you could take a clear direction to pure Compose views then it makes forking and converting much easier!
I'm also happy to start moving towards common code in this repo if thats something you would be interesting in?
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
I noticed allot of the "compose" views are just wrapped older XML views with some Compose wrappers, whats the plan to move to native first compose views?
The reason is I want to fork to make a Stripe KMM library, but the lift is basically writing the whole thing as is unless you can move to pure kotlin and compose.
Describe the solution you'd like
Native Compose views vs wrapped XML views.
Describe alternatives you've considered
Writing everything from scratch...
Additional context
With KMM popularity, I wouldn't expect a KMM library (although that would be super nice), but if you could take a clear direction to pure Compose views then it makes forking and converting much easier!
I'm also happy to start moving towards common code in this repo if thats something you would be interesting in?
The text was updated successfully, but these errors were encountered: