I’m using WeWeb Tables (the native backend) as my data source, not Supabase or Xano.
I have a board where multiple users see the same collection on their phones. When one user updates a row (e.g. assigns themselves to a job by tapping a button), the row should disappear/update for them — but the other users’ screens don’t reflect the change until they manually trigger a fetch. How can i handle it?
Hey @Malin-Alexandru 
Our native backend does not support realtime, no.
A possible workaround would be polling every 5–15 seconds, combined with a backend conflict check to make sure a job can only be assigned if it is still available.
That said, for your use case, I probably wouldn’t recommend relying on polling alone since users seem to be competing for jobs and timing matters. Polling could still leave other users looking at stale data for a few seconds.
Thank you, I have integrated the Supabase plugin for real-time functionality, and for now it works well for my application.
I am currently migrating the tables and I hope everything will function properly, but for the use case described above it already works — I have tested it successfully.
Initially, I tried using the Supabase integration, but only after migrating the tables did I realize that it does not actually support real-time features, and that only the Supabase plugin provides this functionality. 
I hope that in the future the documentation will be updated to reflect the latest features, as it is clear the platform is evolving, but the documentation is slightly behind.
I’m looking forward to future updates, and I hope things will become clearer and more consistent moving forward.
Thank you for your support!