Create a "Flutter for Jetpack Compose developers" page

[jwill]

Description of what this PR is changing or adding, and why:

Adds a page for Flutter for Jetpack Compose devs.

Issues fixed by this PR (if any):

Fixes #5611 and #9051

PRs or commits this PR depends on (if any):

Presubmit checklist

• This PR is marked as draft with an explanation if not meant to land until a future stable release.
• This PR doesn’t contain automatically generated corrections (Grammarly or similar).
• This PR follows the Google Developer Documentation Style Guidelines — for example, it doesn’t use i.e. or e.g., and it avoids I and we (first person).
• This PR uses semantic line breaks of 80 characters or fewer.

[flutter-website-bot]

Visit the preview URL for this PR (updated for commit 6d0f399):

https://flutter-docs-prod--pr11232-for-compose-devs-vg3g9549.web.app

[sfshaza2]

I'm confused. How does this overlap with this: #11219 ?

[jwill]

I'm confused. How does this overlap with this: #11219 ?

#11219 is a targeted flow for an add to app like thing for Flutter developers that need to add a Compose activity.

This PR is speaking more to Compose developers who want to implement flutter and see how their knowledge transfers.

There is minimal overlap.

[jwill]

Hi @jwill! Thanks for writing this! It's a great start.

My primary issue is the focus here should be on how to use Flutter, not how to program better in Compose. ;) I don't think we need so many Kotlin examples.

I actually cut down on the number of examples from the page I modeled it on, Flutter for SwiftUI devs (https://docs.flutter.dev/get-started/flutter-for/swiftui-devs). There are sections on animation and there concepts in that other page that didn't feel essential and were getting into the weeds.

My goal here was targeting a developer who is conversant with Compose and wants to do Flutter. I think it's important to discuss the commonalities to allow them to hit the ground running with real apples to apples examples versus just a textual description.

I can concede that maybe some things can be excerpted more aggressively and places where I listed the two common ways for "A" Compose concept that map to "B" Flutter implementation might be reduced to one. If you are proposing to cut out the Kotlin side of a section totally, it might be better to eliminate the section altogether. Eg The google fonts section could be excised totally with just a pointer to the recently updated typography page.

[sfshaza2]

A couple minor changes, but lgtm

[sfshaza2]

Thanks, @jwill!

[sfshaza2]

@jwill, I want to land this, but the code excerpts are out of date. Can you run ./dash_site refresh-excerpts in your repo and push?

[sfshaza2]

(And also remove it from Draft state.)

[jwill]

I hadn't removed it from draft state because I'm actively working on it and was reworking some things. Was planning to make those edits and post for review.

[sfshaza2]

Oh, @jwill! I misunderstood!