Skip to content
This repository has been archived by the owner on Jun 1, 2024. It is now read-only.

SwiftUI support #120

Closed
theffc opened this issue May 11, 2020 · 1 comment
Closed

SwiftUI support #120

theffc opened this issue May 11, 2020 · 1 comment
Labels
enhancement New feature or request iOS This issue directly affects structure and logic of iOS project

Comments

@theffc
Copy link
Contributor

theffc commented May 11, 2020

Describe the problem

As SwiftUI gets more mature, and iOS 13+ have more adoption, SwiftUI usage will increase, and we need support developers that want to use it.

SwiftUI seems to have good interfacing with UIKit (apple tutorial), but we need to research and test if what we currently have inside Beagle, will work on top of this interface.

One of the main problems that we could have is view positioning/layout. We use Yoga for that, but Yoga only works with UIKit. So, we really need to investigate how to make it work with SwiftUI as well.

Expected behaviour

Beagle should not care if users are using SwiftUI or UIKit, it should work the same way for both frameworks.

@theffc theffc added iOS This issue directly affects structure and logic of iOS project enhancement New feature or request labels May 11, 2020
@lucasaraujo lucasaraujo self-assigned this May 20, 2020
@roip890
Copy link

roip890 commented Jul 22, 2020

I also think SwiftUI can fit better for Server Driven UI because it is declarative and each view it is actually a struct.
Also for android Jetpack Compose can fit in the same way (or DSL with kotlin until compose will be in production).

@lucasaraujo lucasaraujo removed their assignment May 7, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request iOS This issue directly affects structure and logic of iOS project
Projects
None yet
Development

No branches or pull requests

4 participants