As an extension to -d, it would be nice to have some easy to remember, easy to type high level subcommands to flutter run to point to specific device categories when flutter running.

• Running a naked flutter run is likely to bring up a slow target device selector to choose each time which adds friction.
• Even if you're a hobbyist and don't have 10 phones connected to your machine, it's still likely going to be exacerbated by the fact that going forward, chrome and macos etc will be permanently connected devices in your flutter devices list.
• Before running flutter run, you know what device type you want to target. You just likely don't remember what the device name/label is or its serial number.
• flutter run -d <device type> is longer to type, and it often works, but sometimes don't. And when it doesn't occasionally, the loss of confidence makes you not use it.

In the list below

Multiple devices found:
Pixel 3 (mobile)   • 8AXX11BS6                                • android-arm64  • Android 11 (API 30)
iPhone (mobile)    • cdcd493527f1f25a0ac91106540cf58186f2b4f0 • ios            • iOS 14.2
iPhone 12 (mobile) • 9E56D63B-8F4D-4110-A2AF-7D8F9BF8E54C     • ios            • com.apple.CoreSimulator.SimRuntime.iOS-14-2 (simulator)
macOS (desktop)    • macos                                    • darwin-x64     • Mac OS X 10.15.7 19H15 darwin-x64
Chrome (web)       • chrome                                   • web-javascript • Google Chrome 87.0.4280.88
[0]: Pixel 3 (8AXX11BS6)
[1]: iPhone (cdcd493527f1f25a0ac91106540cf58186f2b4f0)
[2]: iPhone 12 (9E56D63B-8F4D-4110-A2AF-7D8F9BF8E54C)
[3]: macOS (macos)
[4]: Chrome (chrome)

neither flutter run -d android, nor does flutter run -d simulator work despite there being only one of each being connected at a time.

• Since Flutter is cross-platform, having more than 1 device of each type being connected may be less frequent.