The Necessity for Bixby to Include device context with vivid details

As Bixby is expanding to other product lineups, I see a necessity as developer to know device's orientation, resolution and device-input-styles. 1) Device Orientation: Sometimes Depending on the orientation there are only certain layout that fits best, otherwise everything becomes either blow out of proportion or vice versa. 2) Device Resolution, expanding upon the previous point [1], Device sometimes are too big for small icon, or image. And so they look damaged 8-bits photos and leads to bad experience. Also, Sometimes with circular faces like "S Watch" you are not certain if something will be cutoff and prevents users from selecting without needed context. users will in this situation might shoot arrow in the dark. So If I know the display-face-geometry then I can adjust the text content, image or layout accordingly. 3) device-input-styles: Users are panic button monsters ;-) , First they use voice to control things, if it fails they will use touch option or remote buttons (actual remote for TVs, Keyboard for Dex Users, Headphone/Hands-Free media buttons, or combination of both) to scroll through list. and we need to adjust how we want out capsules to respond if these buttons are used. for example: vibration or "ting" feedback on Galaxy Home, or respond with details if on handsfree with short bust of detail.