From f7680044bab90c7026130eaecbc734ee7d0f4125 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Martin=20P=C3=BA=C4=8Dik?= Date: Thu, 5 May 2022 16:12:25 +0200 Subject: [PATCH] Update FAQs.md (#1706) --- Documentation/FAQs.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/Documentation/FAQs.md b/Documentation/FAQs.md index 6a62d7a1..42d7b696 100644 --- a/Documentation/FAQs.md +++ b/Documentation/FAQs.md @@ -6,6 +6,7 @@ - [How can I dismiss the keyboard?](#how-can-i-dismiss-the-keyboard) - [How can I get a reference to the `MessageType` in the `MessageCellDelegate` methods?](#how-can-i-get-a-reference-to-the-messagetype-in-the-messagecelldelegate-methods) - [Animations are laggy/Scrolling is not smooth/General poor performance](#animations-are-laggyscrolling-is-not-smoothgeneral-poor-performance) +- [How can I use MessageKit with SwiftUI](#how-can-i-use-messagekit-with-swiftui) ## Why doesn't the `MessageInputBar` appear in my controller? @@ -109,3 +110,7 @@ func didTapMessage(in cell: MessageCollectionViewCell) { ## Animations are laggy/Scrolling is not smooth/General poor performance In general, if you're experiencing performance issues, you should look through the implementation of your MessageKit delegate methods like `currentSender()`, etc to find any expensive/blocking method calls or operations. Some delegate methods are called many times per message rendered and thus if their implementations are not efficient then performance can significantly degrade. Avoid doing blocking activities like synchronous database lookups, keychain access, networking, etc. in your MessageKit delegate methods. You should instead cache what you need. + +## How can I use MessageKit with SwiftUI? + +MessageKit support of SwiftUI is experimental at best and there is no active work being done on adding more support