Composer is a bit unusable on mobile (I only tested Androird)
Hey team, I wanted to test our new chat on mobile, and realised the behaviour of the composer is pretty horrible, if not unusable.
To give you some context:
I was just writing some text using the composer
I have a Samsung galaxy S21+ (Android) - no idea on Apple side, I'll check
What happens?
I guess due to the way input are handled (different from a basic html text area), when I
1/ Use a recommended word on my keyboard fails, it adds the full word and does not replace the start
e.g.
I type "Compo"
keyboard suggests the word "Component"
I click on this suggestion
then what I have in the composer is "CompoComposer" (instead of removing "Compo")
2/ Erasing a word messes up everything
e.g.
When I hold the delete button
it just starts erasing one letter or 2 and then skips the word (which is not erased) and the cursor goes back to the beginning
It's super weird, but we'd really love to be mobile friendly, so this is going to be a must 🙏 Thank you for your help as always ! Keep up the awesome work
Created an issue on Github, but seems like there's more activity here than there, so cross-posting it here as well:
https://github.com/getcord/sdk-js/issues/1
Unfortunately a pretty major blocker for us to go to production with Cord.
Posted on Github, but since there seems to be more activity here, I'm cross-posting here:
https://github.com/getcord/sdk-js/issues/1
Unfortunately a major blocker for us to move to production with Cord.
Hi @Paul Vidal , thanks for bringing this up. We are aware that our composer is far from perfect on mobile. We've done a little work, but not a lot to make it mobile friendly. We can look into this particular issue and see what we find.
@Lauri Lehtmaa , thanks for raising. We will look into your issue as well.
Our focus so far has not been on mobile. We have previously aimed to be ok, but not great there. That is changing, and we have much to do, but right now is not great.
Thanks @Dave as always 🙏 As an engineer, not sure about the technical complexity, but I feel like with this fixed it would at least be usable (even if far from perfect). But as is, it's just unusable so this is why it would be dope to just fix that (not asking more I promise hahaha) 🥲
Ok so after more investigation, I'm a bit lost...
The composer displayed in the doc and on this chat (not sure if it's the same component) work perfectly on my mobile, but not in our app although the composer was not styled or we did not do anything funky with it ...
So your composer works great already on mobile, what could be interfering in your opinion to have such terrible problems?
I've tried composer v1 and v2 here: https://docs.cord.com/components/cord-composer?version=1.0
+ the composer of this community on mobile
-> they worked fine
Pushing my investigation further, it seems it works fine on iOS, so it's really an Android problem, and only on our app...
I've removed all styling and pretty much everything that could interact with the styling and it's still not working (I tested on 2 different android phones).
Any lead would be really appreciated! Mobile is pretty crucial for us as I've said, the investigation continues 😉 Thanks @Dave 🙏
@Paul Vidal , is there a way we can use your app to try and reproduce?
And are you on the v1 or v2 composer? Sounds like you've tried both and they both don't work well.