Did I understand correctly that they used this in an example to push shared updates with its users?

[OBXfund]

In the video demo, there is a segment where the counter is being updated (which is no big deal) but at the bottom there is a push notification. This saves a ton of code by using just a few lines.

[mbrandonw]

Hi @OBXfund, I'm not sure what you are referring to. Can you please provide more information? Which video are you referring to, and at what timestamp?

[OBXfund]

[OBXfund]

Close to 33 minutes: The app is showing a counter. Then, he says “I’m going to open another in Safari.” They are side by side. He updates the one on Safari and it pushes the update to the app version right beside it. This is especially interesting because:

1. There is an update to the app without refreshing the app.
2. There is bidirectional pushes of updates from Safari to App and vice versa.
3. This app was able to be emulated on Safari web browser, which is a major accomplishment in itself.
4. They are creating a virtual database based on SQlite on the fly.
5. Now: imagine Ai hooked to an MCP server that feeds into GRBD. And it is able to persist information OUTSIDE of the app into a web browser.

I suggest watching the entire series of videos for reference.

[mbrandonw]

Hi @OBXfund, I think there may be some confusion. What we are showing is Swift running in the browser via Wasm, and the browser windows are communicating through local storage, which is a very simple storage system built into all browsers. The updates are not being "pushed" in any real sense. It would not work with two browsers on two different computers.

I suggest watching the entire series of videos for reference.

I am the co-creator of that video :) If you want more info on cross-platform Swift you can see our videos here.

[OBXfund]

I thought that you were performing magic! That makes sense now.