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

Send a message (to any destiny) #125

Open
3 tasks
rodrigomonelos opened this issue Nov 16, 2017 · 2 comments
Open
3 tasks

Send a message (to any destiny) #125

rodrigomonelos opened this issue Nov 16, 2017 · 2 comments

Comments

@rodrigomonelos
Copy link
Collaborator

  • See the conversation updated with the sent message.
  • Scroll up to the end of the conversation
  • Keep the keyboard open
@gmarcos87
Copy link
Collaborator

gmarcos87 commented Nov 16, 2017

How is this different from what is already there? What does it mean to any destination?
I also do not think I can force the keyboard to stay open.

@rodrigomonelos
Copy link
Collaborator Author

I agree with you that this was almost already working, but we didn't have any backlog item defining this behaviour.

  • As we talked over Telegram, sometimes messages are not going out, nor being showed. Sometimes they are showed after a while. The first acceptance criteria of this issue defines this behaviour. I added "just after tapping on the send button" to consider the delay.

  • I added an acceptance criteria about seeing the message on the receiver. It could be considered part of Receive a message from App to App #115 also, or we can create a new issue. Let me know if you prefer to have this acceptance criteria somewhere else.

  • I added "to any destiny" on the title to differenciate this backlog item from Send a message to GSM #111, that is focused on reaching GSM phones and not in the behaviour.

  • I think that keeping the keyboard open is valuable. Can you confirm if doing this is a PWA limitation (we sould add it to our list)? If it is not a limitation but is complex, please share that info so we decide toghether if we invest that effort on it now.

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

No branches or pull requests

2 participants