Dart/Flutter under Platforms > Android: which title, etc. to use?

[chalin]

This is a question for the Dart & Flutter folks: @mit-mit @johnpryan @filiph @RedBrogdon @kwalrath @sfshaza2

I'm not sure if you consider this important -- my feeling is that you might care from a branding / marketing perspective (given, e.g., that the Dart SDK is now being shipped as an integral part of the Flutter SDK).

---

Context

In addition to a Languages section, the gRPC website now also has a Platforms section. This is what the left-nav currently looks like for Platforms:

Consider the following attributes of the Kotlin for Android page:

• page title is Kotlin for Android
• short title, which is used in the nav, is just Kotlin, and
• URL path id is kotlin

What would you like that these attributes to be for the Dart/Flutter page under Platforms > Android?

Here are some options for the page title (from which we can most probably derive the other attributes):

• Compact titles
  • Dart -- this would match the title used under Languages but doesn't quite feel right / accurate enough to me
  • Flutter -- this seems most accurate, but would be a mismatch with the use of Dart under Languages
  • Dart/Flutter might be the best choice?
    • Note that I'd likely vote for using dart as the URL path id, regardless of the title, though I'm open to doing otherwise.
• Longer titles:
  • Dart/Flutter for Android
  • Flutter for Android

Any other preferences?

Feedback is most welcome, even if it is "I don't have strong opinions about this".

I wanted to at least ask the question before I create the new site sections and pages.

I'm available for a VC if it'll be quicker to discuss & resolve. Thanks!

cc @zacharysarah @thisisnotapril

[mit-mit]

Thanks for reaching out; we do care about branding :-)

Can you say a little about what kind of docs will be on this new page? It looks like the Kotlin for Android one just has links to the Languages > Kotlin page?

[chalin]

Thanks for reaching out; we do care about branding :-)

Great, that's what I thought.

Can you say a little about what kind of docs will be on this new page?

Initially, it will have a Quick start page describing how to get a gRPC client written in Dart/Flutter running on Android.

It looks like the Kotlin for Android one just has links to the Languages > Kotlin page?

Actually, Kotlin for Android links its own Quick start, which is distinct from the Kotlin/JVM Quick start.

As another example, Android Java has its own Basics tutorial in addition to a Quick start.

Other changes to think about:

• Add Platforms > iOS section, which will have at least a Dart/Flutter quick-start page
• (Tentative) Add a new Dart/Flutter Quick start under Platforms > Web

[chalin]

The Dart/Flutter page (under Platforms > Android), will also be a place to add links to relevant articles, videos, etc. E.g., see Developer stories and talks on the Java page.

[mit-mit]

I believe it will be more natural to consider Flutter a platform, and structure this like this:

Platforms
> Android
  > Java
  > Kotlin
> Web
> Flutter
  > Android
  > iOS
  > Web
    ...

cc @timsneath, whom I believe mentioned this also

[chalin]

Hmm, that isn't the sense in which "platform" is intended here.

As you know, on flutter.dev (and elsewhere) Flutter is described as an SDK which runs on various platforms; here's an excerpt from the Flutter homepage:

Flutter is Google’s UI toolkit ...

Coming from another platform? Docs: iOS, Android, Web, React Native, Xamarin.

I would prefer to be consistent with that terminology.

If I'm understanding correctly, you'd prefer that we use Flutter rather than Dart under Platforms, something like this:

Platforms
> Android
  > Flutter
  > Java
  > Kotlin
> iOS (coming soon)
  > Flutter
  > Objective-c
> Web
  > Flutter
  > JS

Thoughts?

[timsneath]

That *could *work, although now we've exchanged one imperfect analogy with another, listing Flutter alongside languages. And the (coming soon) for iOS no longer makes sense, since it should now be applied to ObjC.

I like to think of Flutter in the same way as Unity -- as a distinct "platform" in its own right that layers on top of underlying targets. Others often treat Unity as a distinct platform, even though it isn't a separate device type. For example, here's Crashlytics: https://firebase.google.com/docs/crashlytics

On Wed, Nov 4, 2020 at 6:33 AM Patrice Chalin [email protected] wrote:

Hmm, that isn't the sense in which "platform" is intended here.

As you know, on flutter.dev (and elsewhere) Flutter is described as an SDK which runs on various platforms; here's an excerpt from the Flutter homepage:

Flutter is Google’s UI toolkit ...

Coming from another platform? Docs: iOS https://flutter.dev/docs/get-started/flutter-for/ios-devs, Android https://flutter.dev/docs/get-started/flutter-for/android-devs, Web https://flutter.dev/docs/get-started/flutter-for/web-devs, React Native https://flutter.dev/docs/get-started/flutter-for/react-native-devs, Xamarin https://flutter.dev/docs/get-started/flutter-for/xamarin-forms-devs.

I would prefer to be consistent with that terminology.

If I'm understanding correctly, you'd prefer that we use Flutter rather than Dart under Platforms, something like this:

Platforms

Android

Flutter

Java

Kotlin

iOS (coming soon)

Flutter

Objective-c

Web

Flutter

JS

Thoughts?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/grpc/grpc.io/issues/491#issuecomment-721766839, or unsubscribe https://github.com/notifications/unsubscribe-auth/AARWL642DD5Y6JVNFMGAVZLSOFQ4NANCNFSM4TI6D2KA .

[chalin]

Ok, thanks for your feedback. Let me see what I can put together. (And apologies for the confusion regarding the "coming soon" comment -- it was meant to reflect that I'll be working on that section later, not that Flutter and/or Objective-C support is pending.)