"Fuchsia's primary app-development language is Flutter, a cross-platform UI toolkit from Google. Flutter runs on Android, iOS, and the web, so writing Flutter apps today for existing platforms means you're also writing Fuchsia apps for tomorrow."
I've looked around a few times this year trying to find a good solution to testing cold-boot deep links in @FlutterDev. Couldn't use widget tests. Couldn't use integration tests. Couldn't use Patrol. So I finally built a solution:
Our @FlutterDev effort to clone Swift UI has taken its first baby step. We've started the inventory process to discover everything available in Swift UI and all the ways they can be configured.
Not to pick on this particular tweet, but this silly mentality just keeps growing. You can do ANYTHING in 2 lines of code when you write 1,000 lines of private code, and then publish 2 lines of code to run it....how do you think CSS works?!
Are you a dev on the @FlutterDev framework team? If so, I'd like to pair program with you. We can record ourselves fixing real bugs in Flutter and then publish the videos for the community to learn how to engage with the process. Please reach out to me!
What is up @FlutterDev's? After a long hiatus from YouTube, I'm back! Today I'm officially launching a new YouTube channel. Subscribe for upcoming Flutter education videos.
SwiftUI is popularizing builder patterns in widget trees. Flutter animate started to make it popular in @FlutterDev. Now SwiftUI fans are pushing it harder for Flutter. It's a bad idea. You shouldn't do it. This is why:
