hello bublers.
I think a video tutorial for messaging, or user to user messages (chat) would really be helpful to those of us who are not very technically good. (The not real twitter tutorial stopped halfway i think).
Since bubble is built with bubble and it has similar features, the video tutorial would be the best cos i there isn’t much clear solution to this in the forums. I am sure many who wants to build interactive social media forums and this feature, internal messaging is very critical.
@emmanuel
thank you
I’m actually creating a full lesson on how to create a basic single chat + 6 or 7 more vids on how to make it better. Won’t be out for a while though so please let me know what exactly you’re struggling with.
Daniel
I am actually learning and practicing with bubble’s several features which i ll need in compiling my app once i fully comprehend them. And the messaging feature is one of the features my app would make use of.
So Okay, I have configured the messaging data types and field>message person, message thread (learn from the not real twitter tutorials), so lets say i have a message or chat icon on a user profile, and the current user clicks on it to send a message to the user. how do i configure the process? with workflows?
If I’m understanding you correctly, really simple!
Create a popup so the current user can create their message. This popup should have a multi line input for the message and a send button.
Now when you click that message icon, the workflow you should select is “show popup”.
Then obviously, in the popup, the send button should create a new message. Once the message has been created, you should “reset inputs” and “hide the popup”.
Make sense?
sure…makes lots of sense…thanks much
Hi,
I don’t know if i will help, but I build something really simple that is pretty cool (at least I think it is :D)
Maybe it’s not high performance standard…
Here is what I did for my app messaging system.
A thread thing with different data type inside :
- creator
- Other user (user) (here you can have a list if you want more people in the thread).
- List of message (this is a list of an other thing which is called message)
Created a thing “message” :
- Message (text)
And that’s it.
Then I have a page with simple stuff…
On the left I have a repeating group showing current users thread (do a search for thread).
I just put a text with the conversation’s creator’s name in each cells. I defined a condition → when current user is this thread creator, then text is other user’s name.
when a cell of the repeating group is clicked, it sends the thread data into an other group, which is on the right of my page.
On the right I have a group thread, with a repeating group inside.
The repeating group data is parent’s group thread’s list of messages.
In each cell’s, I put a text, that is current cell’s message.
And here you got your messaging app system.
The trick then is to have a look like something close to facebook or smartphones.
As I want my current user messages to appear on the right, and my other user messages in the thread appears on the left.
What i did is a bit long but works perfectly.
In my repeating group on the right, I put in each cells, two text showing repeating group messages, one on the left, one on the right.
This texts are not visible on page load.
And I defined for each a condition.
Just define for the left part : If current message’s creator’s is not current user → this element is visible
For the right part : If current message’s creator’s is current user → this element is visible.
Finally at the bottom of the repeating group, I put a multiline input, with an action button “send”.
User can reply in the multiline input.
And here’s the workflow of the button :
- create a new message
- make change to : parent’s group thread and complete “list messages add results of step 1”
- display list data in repeating group messages - data is parent group thread list of messages.
- reset relevant input.
I did some visual customization and here is what I have in my app…
You should always try to avoid having a list of anything as a field if possible. For example, you have a List of Messages for one of your fields in the “thread” table.
This can restrict certain things like searching, sorting, and filtering.
Instead you just add a field called “thread” in your “message” table. This way, you will be able to search for all of the messages in a certain thread and don’t limit your development possibilities.
Once I figured out that this was the best development method, I never looked back. Hope this helps everyone who is currently using a ton of lists in their fields.
can you tell me when thing thread should be created.
Does this video from Coaching Bubble help? I found it very useful when looking at messaging.
Jess
I’ve just launched a chat application tutorial here - nocoder.co
That is a little worrying. Particularly as you are having speed issues.
This was was the case when I had problems with filtering limitations. That however, isn’t the case with the project I mentioned in my latest post. I use both list and data fields. Even though this slows down the workflow by a fraction of a second, I then have the flexibility to fetch data more effectively.
UPDATE: Use both data fields and lists. For complex filtering (at the time), Bubble’s list fields couldn’t handle more complex searches. If you’re looking for fast data fetches, you should search with lists, not an entire database table.
Hi
When we add invisibilty condition, repeating gp height collapses on the invisible msgs. This leads to msgs going up & down. How you prevent repeating group height from collapsing when msg is not visible.