Looking for Desktop Engineer (Electron, TS, React) for Private Client

[Kstieo]

We need a lightweight desktop software solution to connect to an external communication protocol.

Focus areas:

• Zero bloat: strictly one-on-one text exchange, no public directory or multi-channel complexity.
• Direct authentication flow via standard credentials/OTP.
• Fast, typed IPC between the UI and native background processes.
• Soft-delete visual markers: retain the original body text with a clear "message deleted" tombstone.

Prior experience with real-time sockets or native API libraries is strongly preferred. PM with relevant work examples and your TG handle for fast follow-up.

 

[jonh_smith]

We need a lightweight desktop software solution to connect to an external communication protocol.

Focus areas:

• Zero bloat: strictly one-on-one text exchange, no public directory or multi-channel complexity.
• Direct authentication flow via standard credentials/OTP.
• Fast, typed IPC between the UI and native background processes.
• Soft-delete visual markers: retain the original body text with a clear "message deleted" tombstone.

Prior experience with real-time sockets or native API libraries is strongly preferred. PM with relevant work examples and your TG handle for fast follow-up.

Hey, saw your post about the barebones desktop messenger.
I mostly build backend pipelines and socket-heavy automation, which translates pretty directly to what you need here: fast, typed IPC without the usual desktop framework trash.
To hit that zero-bloat mark, the logical move is decoupling. We keep a native background daemon handling the actual work (local SQLite, socket connections, hitting the OS keychain for the OTP token). The UI should just be a dumb, thin layer. They talk via strict IPC, like Protobuf.
The soft-delete tombstone thing is straightforward. It's just state sync. The original text stays in the local DB. We flip an is_deleted flag, push the event over the socket, and the UI throws the visual marker over the string.
If you want someone who actually cares about keeping the data flow clean and the memory footprint low, hit me up. TG @nerpafish