I have just put my first version of my app into testflight which used a loading screen to determine whether to link to an existing conversation or to create a new one. This worked effectively, however it took about 8 seconds to load which I would rather avoid.
Have been trying to get it so that I can just link directly from the list of users to start a conversation with and the closest I have got so far is:
have two buttons (one inside of a conversations list nested in the users list) in the list of users. One creates a conversation and one links to existing.
Both these buttons work well and show when they need to be based off of conditional visibility.
What I am struggling with is that when I try to put them in the same spot in the list, they make the list display weirdly which I assume is due to overlapping components inside of the list.
Is there a way to make this work better, or should I just go back to the loading screen with countdowns on it.
Would you be able to include some screenshots or a screen recording (much better!) on how you configured this part in the builder vs how it’s displaying in the app?
Thanks for your reply. I went back to the loading screen and changed it slightly and found that is a bit quicker now (one set of actions is now on screen load and then one on a countdown in a list of conversations).
With the buttons inside of the list, I would much prefer to have it so that the whole list item is clickable and takes the user to the messaging screen. I have tried to do this by adding a rectangle on top of the list, making it sometimes visible, and then making that rectangle into a list of conversations between logged in user and current user. Then on the original list of users there are actions to create and link to a new conversation. That worked fine but still left me with the same display issues.
(I forgot to add the link action in the video but added it afterwards)
I guess that won’t work. (based on your recording) In the past I remember I tried having the same group as 2 in the same users list (like rectangle group and then near to that a duplicate of that rectangle group stacked, inside the same list) and then adding the visibility conditions to those 2 rectangle groups + plus actions. (second group as a nested list for conversations collection) Same behavior as adding two buttons but had slight layout issues and a bit slow to process. I most times link to their profile page and add the 2 buttons. Sometimes adding those buttons inside the users list but trying to avoid nested lists to maintain a good performance of the app which sometimes using a loading screen. I think some kind of link action that finds a record from a specified collection by IDs as inputs and then pass that found record data to be available in the next screen would be a good addition. I’ll take a note on that!
Anyone have any other ideas? I would love to hear!
