Android & server development
13 / Secure messenger · System development
DUAL LOCK
Connecting device and server, authentication and encryption. An independent libsignal-based Android messenger and local server development project.
The question
A starting point.
The core task was to separate two-stage authentication and encrypted messaging across the mobile app and server. The architecture distinguishes device-side encryption from opaque messages retained by the server.
- Project type
- Android & server development
- Scope
- Android & encrypted-messaging architecture / Authentication & server components / Local integration & validation structure
- Period
- 2026.09–10
Design decisions
Less noise.
More intention.
The Android client, authentication, and message relay have distinct responsibilities, with messaging based on libsignal. A native Argon2 provider and connection controller form separate layers.
Local service readiness, debug builds, device-screen validation, and public distribution are managed as separate milestones. Development artifacts are distinguished from a general-user release.
The output
The idea,
in a tangible form.
The work includes an Android debug build, authentication and relay components, and a local native provider. The case covers software architecture and development artifacts; device-screen round trips and a public release remain separate milestones.
Explore a direction for your brandNext project
14 / 21B2B data portal · Early architecture · Architecture & initial scaffold