Our great sponsors
-
-
SurveyJS
Open-Source JSON Form Builder to Create Dynamic Forms Right in Your App. With SurveyJS form UI libraries, you can build and style forms in a fully-integrated drag & drop form builder, render them in your JS app, and store form submission data in any backend, inc. PHP, ASP.NET Core, and Node.js.
Other than that, I don't think there's much difference between maintaining a bridge and maintaining your own translation layer for your own UI. To seal the deal for me, https://github.com/signalapp/Signal-Desktop/issues/3410 would essentially obsolete all this effort - right? Once it's running natively there's no need for an always-slightly-behind third party implementation.
I've been using Signald for the last few months and then bridging it to Matrix. I think building exactly the same thing based off the Rust client is the most compelling option (and probably something I'd be interested in working on as well!). Given that a double-puppeted Signal account can be used with Matrix today, it'd be a shame to invest in Signal-specific UI. There are multiple "nearly there" Matrix clients that can work on the pinephone and others. You could even bridge libpurple to Matrix if you're into that ecosystem.