Paul HittandClaude Opus 5
5bbc328076
0.26 carried the palette, the 2dp corners and the gradient helpers, but every screen still drew a plain headline and sat inside a 20dp margin, so the app looked like the old one in new colours. This is the structural half. PortalChrome.kt is the new furniture: the navy screen header with the FLAMENET eyebrow, the maroon header a conversation wears because a conversation is the Messenger channel, the ruled section band, the squared avatar tile, the gold unread count, the full width list row, and the raised control face. Signed in, the screen is now flush to its edges. Chrome, bands and rows are full bleed on the portal; a margin around them turns each one into a card, which is the single change that would undo the rest. Prose asks for its margin back with PortalBody. Buttons and chips are drawn rather than configured. Material takes a flat container colour, and a flat fill beside a beveled face is the seam that gives a half done restyle away. Three defects found while looking at the renders: Mute and Report on a story were painted Palette.Mist, the pale page ground used as ink, so they were nearly invisible on white. The story action row overflowed and broke Report across two lines mid-word. It wraps now. The Stories tab icon was Icons.Outlined.Circle, a placeholder that drew an empty ring naming nothing, and the one round shape left in a squared interface. The screenshot harness no longer pads its full screen shots, because the app does not, and photographing a layout the app does not have is how a suite goes green while proving nothing. A shot of the tab bar is new: it was rewritten for the portal chrome and nothing rendered it. 1474 unit tests green across engine, client, obfs4 and app. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Flamenet Messenger. Android
The Android app, and the two libraries under it. The product's site is at https://flamenetmessenger.com.
engine/ the protocol: X3DH, Double Ratchet, sealed sender, safety numbers,
key transparency. Plain Kotlin/JVM — no Android in it at all.
client/ the relay transport: HTTP, auth, the §8 routes.
app/ the Compose app.
interop/ the cross-engine driver; not shipped.
engine and client are deliberately plain JVM libraries. The protocol has
nothing to do with Android, and keeping it off the platform means their tests
run anywhere a JVM does, no SDK, no emulator, no device, which is also what
lets them gate in CI on Linux:
./gradlew :engine:test :client:test
The app's own unit tests need the Android SDK but still no emulator (Robolectric):
./gradlew :app:testDebugUnitTest
Where it stands
PARITY.md is the definition of done for this app, read that, not this. Every row there names the iOS file it came from so it can be re-checked rather than trusted. Headlines: messaging, groups, attachments, voice notes, stories, calls, sealed sender, key transparency and the encrypted vault are built and tested, and a cross-platform round trip against iOS is verified.
If a claim here ever disagrees with PARITY.md or with the tree, believe those, and fix this.
Why the engine came first, and is held to the vectors
An Android client needs the protocol implemented a third time, and the third
implementation is the one that finds the places where the specification says
less than the two existing engines quietly agreed on, but only if it is
written against the spec and the published vectors rather than against a
reading of our own Swift and JavaScript. So the engine is held to
test/vectors/protocol-v1.json in
flamenet-e2e, the same file the
other two engines are checked against, read from that repository rather than
copied here, because a copied vector file drifts and a drifting vector file
stops being a check. PublishedVectorsTest looks for it beside this checkout
and fails loudly if it cannot find it; FLAMENET_VECTORS overrides the search.
Two implementations that agree may both be wrong in the same way, especially when one was written while reading the other. The audit-path ordering in §19 is the worked example: a top-down reading of a bottom-up path produces the correct root for every left-spine index, so it passes any test that only checks index 0. The vector file pins a right-descending index for that reason, and the Kotlin tests assert both that the published path verifies and that the same path reversed does not.
If this engine ever disagrees with the file, the interesting question is which of the three is wrong, not this one by default.
Contributing and security
- CONTRIBUTING.md, building (JDK 21,
JAVA_HOMEis not optional on a Mac), the test gate, and the platform traps that cost an hour each. - PARITY.md, what iOS does, what this does, and what is left. It is the definition of done for this app.
- SECURITY.md, threat model and where to send a vulnerability report. Not an issue tracker matter: security@flamenetmessenger.com.