Capability to automatically detect the at symbol "@" for mentions (maybe against a collection of 'contacts') and the ability to detect the pound symbol '#' for hashtag creation.
Currently, the Avatar property is a string for a path, this is problematic and only support two scenarios (file and uri paths).
I'm requesting that this be changed to be of type ImageSource, which matches the paradigm used by all other Image controls in Xamarin.Forms. This would allow stream and byte sources as well as file and uri paths.
This doesn't have to be a breaking change, you can use an implicit conversion just like Xamarin.Forms Image source does. The only disruption would be if anyone assigned the string value in code instead of a binding.
Currently, the HealthcareAssistant demo is lacking in features. For example there are no pickers or any commonly used cards.
Although the TravelAssistant demo does have these features implemented, we would specifically like to see the HealthcareAssistant implementation of them. As it is now, we find it lacking and not a helpful demonstration.
To illustrate what I mean, please refer to the attached screenshot as just one of the possible responses that not currently covered by the example.
On iOS, need a way to dismiss the keyboard that doesn't require tapping the "Return" key, On Android, this is done with a tap gesture. On iOS this is usually done with a swipe down gesture.
When the keyboard is displayed (after clicking into the entry), the messages listview is not resized,so the first messages are hidden and the user cannot scroll to them
The Conversational UI is a nice control , but it is limited. The Following will make life easier for the developer .
1) A Custom Template that can allow the user add buttons and customize the send button , like whatsup does, it has "Voice Note" , "Image Attachments" etc..
2) Also allow the user to be able to add images on the chat control itself.
When iOS 12.1 software keyboard is toggled, the entry bar doesn't shift to the right height.
In the attached gif, we can see the entry bar shifted up, but not high enough to stay above the keyboard. As a result, the keyboard blocks the entry bar
This would allow the user to set advanced Entry properties and layouts. One such use case was requested: Set the Entry's MaxLength and add an inline "215/300" to inform the user of how many characters are left for that message.
When there are more messages in Chat on initial load, it should scroll to show the most recent ones.
The problem is reproduced sporadically on different platforms or devices. As a workaround you would need to add the same images to platform projects. Please find the images attached.