Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature Suggestion] TextField Composable for Wear OS #1563

Open
uripre opened this issue Aug 8, 2023 · 4 comments
Open

[Feature Suggestion] TextField Composable for Wear OS #1563

uripre opened this issue Aug 8, 2023 · 4 comments
Labels
enhancement New feature or request

Comments

@uripre
Copy link

uripre commented Aug 8, 2023

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.

@yschimke
Copy link
Collaborator

yschimke commented Aug 8, 2023

Discussed here

#1355

We could implement something, but basically combining a text input with the launch for result.

@uripre
Copy link
Author

uripre commented Aug 8, 2023

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.

@Fra078
Copy link

Fra078 commented Aug 9, 2023

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

@yschimke yschimke added the enhancement New feature or request label Sep 19, 2023
@oas004
Copy link
Contributor

oas004 commented Sep 26, 2024

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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

4 participants