Strategies for building cross-platform messaging apps? #54
Replies: 1 comment 11 replies
-
Hello! This is a great question and one I am currently trying to work on right now. For context I have the far-off dream of potentially integrating reticulum as a transport layer for the messaging app Briar. Briar is a JVM based codebase so I am running into this same issue. My current approach is something I call "Reticulum Open Bridge" which is essentially a TCP sever that listens on a local socket, and relays data to and from RNS. This allows any programming language with a socket library to send and receive data over RNS, and makes writing new RNS libraries simple (with the downside that programs using these 'lite' libraries need to control the ROB process). This idea mirrors I2P's SAM API. Also worth noting there are frameworks for python that allow for apps that target Android, and Desktop (not sure about iOS support). There is a gui messenger using LXMF available for Android Linux and MacOS right now: https://github.com/markqvist/Sideband Eventually there is likely going to be some sort of RNS C implementation which could be packed into a binary and set up to be used in other apps like the current tor binaries. For example, Briar uses tor by executing and controlling a tor binary from within it's Java/Kotlin application. |
Beta Was this translation helpful? Give feedback.
-
It seems like all of the Reticulum SDKs are written in Python. The code is very clean and readable, but this presents a problem for those that would seek to build a cross-platform messaging app.
For example, I think the most popular cross-platform frameworks today are React Native and Flutter. How do we include LXMF into a React Native or Flutter application?
I have the following questions:
Beta Was this translation helpful? Give feedback.
All reactions