Files
simplex-chat/apps/multiplatform
Narasimha-sc 6525367493 android, desktop, ios: show pending invitee's support messages in chat list preview
A member pending review has no main scope to write in, so their "chat with
admins" messages are what the group's row in the chat list should show.
New support items reach the row since #5909 and #7072; this covers edits,
status changes and deletions of those items, the invitee's own edits, and
which item the row shows.

Chat list:
- upsertChatItem and removeChatItem use ChatInfo.inMainChatList (added on
  iOS here, as in Kotlin) instead of the main-scope test, so edits, status
  changes and deletions of a support item reach the row that shows it; only
  a main scope chat can still be added to the list. On iOS, an item not
  loaded in the open chat replaces the preview only for main-scope items.
- previewItem, extracted from addChatItem on both platforms, picks the
  row's item: for a pending invitee the onboarding events (pending review,
  "end-to-end encrypted" info, member connected) do not replace a message,
  and a message replaces them, whatever their timestamps; otherwise the
  later item wins.

Sent edits reach only the active chats context, so ChatModel.upsertSentChatItem
updates the primary context as well when the active context is a support chat
shown in the main list, as addSentChatItem does for new items. Cross context
dispatch stays with the caller, as in processReceivedMsg; no ChatsContext
method touches the other context.

The chat preview row shows the message instead of the "reviewed by admins"
status when there is text or, with previews enabled, content that is rendered
without text (a media item without a caption).
2026-10-19 08:39:55 +00:00
..
2023-06-29 12:53:11 +01:00

Android App Development

This is a guide to contributing to the develop of the SimpleX android and desktop apps.

Project Overview

This is the Kotlin Multiplatform (KMP) mobile and desktop client for SimpleX Chat, sharing code between Android and Desktop (JVM) platforms using Compose Multiplatform for UI.

Setup

The desktop app builds nanohttpd from a submodule, Android does not use it. Before building the desktop app on a fresh checkout:

git submodule update --init --recursive

Build Commands

# Android debug APK, assembleGoogleDebug builds the flavor with the Play Billing dependency
./gradlew assembleFossDebug

# Android release APK, distributed via F-Droid and GitHub
./gradlew assembleFossRelease

# Android app bundle, distributed via Google Play, includes Play Billing
./gradlew bundleGoogleRelease

# Always name the flavor for releases. The aggregate tasks (build, assemble, assembleRelease,
# bundle, bundleRelease) fail on purpose: they would package a release APK with Play Billing,
# or an app bundle without it.
# The fdroiddata recipe defaults to assembleRelease and must be changed to assembleFossRelease.

# Desktop distribution (current OS)
./gradlew :desktop:packageDistributionForCurrentOS

# Run desktop/JVM tests
./gradlew desktopTest

# Run Android instrumented tests (requires connected device/emulator)
./gradlew connectedFossDebugAndroidTest

# Build native libraries for all platforms
./gradlew common:cmakeBuild -PcrossCompile

# Clean build
./gradlew clean

Architecture

Module Structure

  • common/ - Shared code (Compose UI, models, business logic)
    • src/commonMain/ - Cross-platform code
    • src/androidMain/ - Android-specific implementations
    • src/desktopMain/ - Desktop-specific implementations
  • android/ - Android app container
  • desktop/ - Desktop JVM app container

Key Components (common/src/commonMain/kotlin/chat/simplex/common/)

  • model/ChatModel.kt - Main state container with reactive properties (MutableState, MutableStateFlow)
  • model/SimpleXAPI.kt - API bindings to Haskell core library via FFI
  • platform/Core.kt - FFI interface to native libapp library
  • platform/ - Platform abstraction layer (expect/actual pattern for Android/Desktop specifics)
  • views/ - Compose UI screens organized by feature (chat, chatlist, call, usersettings, etc.)
  • ui/theme/ - Design system (colors, typography, shapes)

Native Integration

The app calls into a Haskell core library via JNI/FFI:

  • CMake builds in common/src/commonMain/cpp/android/ and cpp/desktop/
  • Cross-compilation toolchains in cpp/toolchains/
  • Built libraries go to cpp/desktop/libs/ (organized by platform)

Configuration

local.properties (create from local.properties.example)

compression.level=0          # APK compression (0-9)
enable_debuggable=true       # Debug mode
application_id.suffix=.debug # Multiple app instances on same device
app.name=SimpleX Debug       # App name for debug builds

gradle.properties

Contains versions (Kotlin, Compose, AGP) and app version info. Key settings:

  • kotlin.jvm.target=11
  • database.backend=sqlite (or postgres)

Testing

Tests are in:

  • common/src/commonTest/kotlin/ - Cross-platform tests
  • common/src/desktopTest/kotlin/ - Desktop-specific tests (run with ./gradlew desktopTest)
  • android/src/androidTest/ - Android instrumented tests

Resources & Localization

  • String resources: common/src/commonMain/moko-resources/base/strings.xml + 21 language variants
  • Uses Moko Resources (dev.icerock.moko:resources) for cross-platform resource management
  • The adjustFormatting gradle task validates string resources during build

Platform-Specific Notes

Android

  • Min SDK 26, Target SDK 35
  • NDK 23.1.7779620
  • Supports ABI splits: arm64-v8a, armeabi-v7a
  • Deep linking requires SHA certificate fingerprint in assetlinks.json (see README.md)

Desktop

  • Distributions: DMG (macOS), MSI/EXE (Windows), DEB (Linux)
  • Mac signing/notarization configured via local.properties
  • Video playback uses VLCJ

Gotchas

In order for the SimpleX app to be automatically adopted for opening links from https://simplex.chat the SHA certificate fingerprint for the App installed on the phone must be in the hosted assetlinks.json file on simplex.chat.

The accepted fingerprints are in the sha256_cert_fingerprints list.

To find your SHA certificate fingerprint perform the following steps.

  1. Build and install your development version of the app as usual
  2. From the terminal in Android studio run adb shell pm get-app-links chat.simplex.app
  3. Copy the signature listed in signatures in the result
  4. Add your signature to assetlinks.json in the website repo and make a PR. On approval, wait a few minutes for the changes to propagate to the public website and then you should be able to verify SimpleX.

More information is available here. If there is no response when running the pm get-app-links command, the intents in AndroidManifest.xml are likely misspecified. A verification attempt can be triggered using adb shell pm verify-app-links --re-verify chat.simplex.app.

Note that this is not an issue for the app store build of the app as this is signed with our app store credentials and thus there is a stable signature over users. Developers do not have general access to these credentials for development and testing.

Adding icons

  1. Find a Material symbol in Rounded category.

  2. Set weight to 400, grade to -25 and size to 48px.

  3. Click on the icon, choose Android and download XML file.

  4. Update the color to black (#FF000000) and the size to "24.dp", as in other icons.

For example, this is add reaction icon.