diekuswhat started many years ago as a simple idea with the Samsung folks and @torgo, is today an OT. My first ever spec: I have a special place in my heart for the #DevicePostureAPI, and still remember seeing a prototype many years ago on an OG Samsung Galaxy Fold, behind a flag and getting extremely excited that I had contributed to the web platform in a meaningful way. 💖 https://developer.chrome.com/blog/foldable-apis-ot https://www.youtube.com/shorts/_sikA5kEIwQ Kudos to my co-editors, @kennethrohde and Alexis from Intel.
Thomas Steiner 
Nicolas Hoizey@tomayac thanks!
I think it would be a nice addition to the blog post introduction to say that this is a continuation of work done these last few years by multiple teams/companies, instead of “Chrome is introducing two new APIs”.
When I stared using it (as shown in https://nicolas-hoizey.com/notes/2021/12/15/1/ ), it was mainly based on content/tutorials from Microsoft, for the Surface Duo, including https://learn.microsoft.com/en-us/dual-screen/introduction
@tomayac you're welcome! 🙏
@nhoizey @tomayac @torgo @kennethrohde In the case of Device Posture API, it's a Samsung initiative. This even shipped on Samsung Internet years ago. Viewport Segments is a Microsoft effort. It has been supported on the Duo for a while as well. Saying "Chrome is introducing two new APIs" does not make justice nor recognises the multi-vendor work behind the APIs... and kinda paints the idea Chrome did them... which is not very nice. Appreciate the callout @nhoizey and you looking at it @tomayac 🙏🏼
Alexis Menard@diekus @nhoizey @tomayac @torgo @kennethrohde the blog post was authored by me as well, and I'm not a Google employee so saying it feels like "Chrome" did it is reaching out a bit IMHO. Microsoft, Samsung are acknowledged in the specs, explainers, implementation, commit messages and more. Yes, it was work that Samsung and Microsoft started but Intel picked up everything for a least a year or two, including implementing Android which Intel has no interest in.
@diekus @nhoizey @tomayac @torgo @kennethrohde Yes it shipped on some devices (Edge Android with Duo/Duo2) and Samsung Internet but the Android implementation never made it upstream. So, in a sense these APIs are new in Chrome because they never worked even behind a flag. Anyhow we reworded the blog post and added a big sign about the collaboration.
@darktears the issue was mainly that “Chrome is introducing two new APIs“ sounded like Chrome was the initiator of these APIs.
Both the new “Chrome is trialing two APIs” and the info box about collaboration with other vendors are really better, thanks a lot for this! 🙏
@nhoizey now I hope you'll try them :)
@darktears I will, for sure! I already use the Viewport Segments API in CSS, the Device Posture API is a great addition.
Unfortunately, I can only test in devtools, I don't have a foldable device… 😅
@nhoizey that's why I beefed up DevTools 😀 . You now can emulate two new devices. A foldable PC and a foldable Android which will set the segments. You can also change the posture in the devtools for both of them. And you can see where the hinge/fold would land in your page.
@darktears awesome, thanks!
@nhoizey @darktears @diekus @torgo @kennethrohde Was about to say this: the intro was updated and there's a prominent aside with acknowledgements of the contributors. https://developer.chrome.com/blog/foldable-apis-ot?hl=en
@darktears @nhoizey @tomayac @torgo @kennethrohde It was a matter of perception. Devs don't know you work at Intel nor read commits nor specs. I know there was no ill intention, but the wording seemed unfair to the larger work done by several vendors like Samsung and Microsoft. The article on the Chrome blog made it look like it is a Google led API. Anyway, appreciate the note you've added and happy there's an OT on the way.