Read on Twitter
Seeing a lot of confusion around Compose and SwiftUI.
A few clarifying facts:
1. Compose was announced publicly before SwiftUI was
2. Apple _probably_ started working on SwiftUI much earlier than Google did Compose (guessing at least an extra year)
(more in
https://abs.twimg.com/emoji/v2/... draggable="false" alt="🧵" title="Thread" aria-label="Emoji: Thread">)
A few clarifying facts:
1. Compose was announced publicly before SwiftUI was
2. Apple _probably_ started working on SwiftUI much earlier than Google did Compose (guessing at least an extra year)
(more in
3. Google had been working on Compose for ~18mo as of announcement in May 2019
4. If you& #39;re looking for influence in Compose& #39;s design, you should look at Flutter and React more than SwiftUI.
5. I& #39;m _very_ impressed by SwiftUI and think it& #39;s a great direction for iOS!
4. If you& #39;re looking for influence in Compose& #39;s design, you should look at Flutter and React more than SwiftUI.
5. I& #39;m _very_ impressed by SwiftUI and think it& #39;s a great direction for iOS!
These projects take _time_. Seriously.
And "influenced by" does not mean "clone of".
Calling any of these things a "clone" of the other is reductive and discounts a lot of the work and thought that people put into it.
And "influenced by" does not mean "clone of".
Calling any of these things a "clone" of the other is reductive and discounts a lot of the work and thought that people put into it.
This is a really exciting time.
Declarative component-based UI toolkits are here to stay, and we now have _several_ very talented teams of people that are investing an awesome amount of brainpower into innovating on this programming model.
Declarative component-based UI toolkits are here to stay, and we now have _several_ very talented teams of people that are investing an awesome amount of brainpower into innovating on this programming model.
