You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In my opinion, it's crazy that we have to implement text input with startActivityForResult/RemoteInputIntentHelper etc. I think there should be a TextField composable to offer this functionality out of the box.
Would love to hear thoughts.
The text was updated successfully, but these errors were encountered:
Thanks for the reference, Yuri. I think we should. Even if the behavior of TextInputs on Wear OS is to launch a popup over the entire screen and then return to the app, I think this behavior should be seamlessly encapsulated in a TextInput component.
My suggestion is to implement a composable which use KeyboardInputController classes because RemoteInput is not always supported on non-wearOS wearables like some Huawei watches and Oppo. Now is difficult to publish apps stores different from Google play because of this problem
Bringing the discussion from #2395 into here to discuss requirements for this component. As @luizgrp mentioned here #2395 (comment). "This intent is for gboard, which doesn't come pre-installed in every watch ", how would be the best way to handle this from a UX perspective? If we where to use the KeyboardInputController is that already handling that perhaps?
In my opinion, it's crazy that we have to implement text input with startActivityForResult/RemoteInputIntentHelper etc. I think there should be a TextField composable to offer this functionality out of the box.
Would love to hear thoughts.
The text was updated successfully, but these errors were encountered: