Closed Corvus400 closed 2 months ago
@takahirom I've been thinking about the task. If you know of an easier way to accomplish this, I would like to follow the task accordingly. 🙇
Can we open a Swift screen from Android? I think we can pass a lambda from Swift, so there might be a way.
@takahirom I will try to see if I can't use the existing iOS code to handle the part of the code that opens the license screen. However, to show the potential of Compose Multiplatform, I will try to implement the described procedure once the existing license screen can be displayed. 🫡
I think it is finished. Let me know if I'm wrong.
@takahirom If you do not need to use the same license screen for Android/iOS, then you are done. :saluting_face: If you do this task, you will have the advantage of using a common screen for iOS and Android. However, there is a concern that if we execute this task, we do not know if we can make CI pass the task as long as we treat JSON as an artifact. :thinking:
@takahirom If you don't need to make the license screen conform to Compose Multiplatform, you can finish it, but what should you do? 🤔
I think creating a screen is not that difficult, but generating license information for both iOS and Android libraries would be challenging.
There are still some major issues with Compose Multiplatform, so I'm going to focus on solving those issues and not do this task this time. 🫡
Why is this necessary?
The following is an overview of the list of tasks required to complete the task.
Link