There's not a trait for it yet, but Smithy is designed to be auth agnostic so new auth traits can be added by anyone. There's a meta-trait called authDefinition[0] that you can apply to your own trait to indicate that it's an auth trait. With that your trait would show up anywhere else auth traits are found in the Smithy tooling. We're designing the code generators to be extensible enough that you could then fairly easily implement just the necessary bits.
It’s not popular because it’s incredibly expensive. For $12/month you get:
- No ads
- Minor usability improvements to the app
- “premium” content
- YouTube Music
The “premium” content is trash and YouTube Music is the worst music app with any significant effort put behind it, in addition to being a significant step down from Google‘s previous offering.
If only it were that cheap. The cost in the US is $12/month which is ridiculously high considering their “premium” content is garbage as is YouTube Music which is forcibly bundled in.
Personally, I absolutely hate 3D Touch. I've never been able to get the hang of the distinction between it and a long press, so something as simple as moving apps around or selecting a character with an umlaut is incredibly frustrating.
I work at Amazon and I don't believe that applies here. There certainly is an expectation that you can coordinate increasingly broad efforts as you rise through the ranks, but the focus isn't on launching new products (in my experience). Impact can be anything that is positive and measurable. At the end of the day if you make the company $1million then it doesn't really matter where you do it.
It's a pretty neat tool. I've played around with it a lot, and it's used in the aws-shell[0] to a very similar effect as the OP. (Disclaimer: I work for aws and have contributed to the aws-shell.)
[0]: https://awslabs.github.io/smithy/1.0/spec/core/auth-traits.h...