Twake Chat Client
Website • View Demo • Report Bug • Roadmap • Translate Twake
Twake Chat is an open source, decentralized chat app based on the Matrix protocol. It was developed by Linagora. Twake Chat is a good option for individuals and organizations who are looking for a secure and decentralized chat app. It is also a good choice for developers who want to build their own Matrix-based chat apps.
Features
- Send all kinds of messages, images and files
- Voice messages
- Location sharing
- Push notifications
- Unlimited private and public group chats
- Public channels with thousands of participants
- Feature rich group moderation including all matrix features
- Discover and join public groups
- Dark mode
- Custom themes
- Hides complexity of Matrix IDs behind simple QR codes
- Custom emotes and stickers
- Spaces
- Compatible with Element, Nheko, NeoChat and all other Matrix apps
- End to end encryption
- Emoji verification & cross signing
- And much more...
Development
Please make sure to run the following command at first, to verify your code before each commit:
bash scripts/config-pre-commit.sh
Requirements
- Flutter 3.38.9
You can at any moment verify your flutter installation using:
flutter doctor -v
Web
If you only plan to work on the web target we recommend installing Google Chrome as it is the default supported target (Flutter being developped by Google).
It is also required to have a web ready version of libolm available in the assets/js/package folder. You can build a version using:
docker run -v ./assets/js/package:/package nixos/nix:2.22.1
# within the docker
nix build -v --extra-experimental-features flakes --extra-experimental-features nix-command gitlab:matrix-org/olm/3.2.16?host=gitlab.matrix.org\#javascript
cp /result/javascript/* /package/. -v
exit
# back on your host
sudo chown $(id -u):$(id -g) ./assets/js/package -Rv
Android
- An implementation of JDK 17 (tested with openjdk-17.0.13+11)
- (Optional) Android Studio
- An Android SDK with:
- Android build tools: 34.0.0
- Android platform: 31, 32, 33, 34, 35
- CMake: 3.22.1
- Android NDK: 26.1.10909125
- Google APIs: enabled
Note: Gradle will try to install the JDK 8. If for any reasons the operation failed, try to install your own and use this method to tell Gradle where to find it.
Linux
- Lib JsonCPP
- Lib Secret
- Lib RHash
- Lib WebKit 2 GTK
- Lib OLM
If needed, a complete list is available in the flake.nix.
On Ubuntu, the following command should install all the required elements:
sudo apt install libjsoncpp1 libsecret-1-dev libsecret-1-0 librhash0 libwebkit2gtk-4.0-dev libolm3
In addition, the Linux build requires Rust. For macOS or Linux, execute the following command in a terminal emulator:
curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh
For Windows, you can use the Rust Installer.
In case you have Rust already installed, make sure to update it to latest version:
rustup update
devenv.nix
A devenv.nix is provided in order to ease the process of setting up your dev environment. Check out the install instructions: https://devenv.sh/getting-started/
Then you can use devenv shell to fire up your environment.
This can be automated thanks to: [nix-direnv](https://github.com/nix-community/nix-direnv/)
Supported platforms:
- Linux x86_64
- MacOS aarch_64
- MacOS x86_64
- Windows WSL
Configure the app
In order to run the web target you must provide a default configuration file. This can be done by copying the config.sample.json to config.json.
Here is an example working with matrix.org:
{
"application_name": "Twake Chat",
"application_welcome_message": "Welcome to Twake Chat!",
"default_homeserver": "matrix.org",
"privacy_url": "https://twake.app/en/privacy/",
"render_html": true,
"hide_unknown_events": true,
"issue_id": "",
"app_grid_dashboard_available": false,
"homeserver": "https://matrix.org/",
"platform": "localDebug",
"default_max_upload_avatar_size_in_bytes": 1000000,
"dev_mode": true,
"qr_code_download_url": "https://sign-up.twake.app/download/chat",
"enable_logs": true,
"support_url": "https://twake.app/support",
"cozy_external_bridge_version": "0.16.1"
}
Running the code
Before running the app, please update the dependencies:
flutter pub get && flutter pub run build_runner build --delete-conflicting-outputs
Now you can run the project:
flutter devices # To list available run targets
# flutter run -d <device>, e.g:
flutter run -d chrome
Build
Please use the helper script corresponding to your target in order to build:
Web
./scripts/build-web.sh
Linux
# ./scripts/build-linux.sh ## For release purposes
./scripts/build-linux-debug.sh
Android
# ./scripts/build-android-apk.sh ## For release purposes
./scripts/build-android-debug.sh
Performance Profiling
Why Chrome DevTools instead of Flutter DevTools?
Flutter DevTools is designed for native (iOS/Android/Desktop) profiling and provides frame-level insights via the Dart VM. On Flutter Web however, the Dart code is compiled to JavaScript and runs inside a browser engine. Flutter DevTools cannot profile the JavaScript execution, browser rendering pipeline, or web worker scheduling.
Chrome DevTools Performance panel is the right tool for Flutter Web because it captures the actual browser behavior: main thread long tasks, animation frame durations, garbage collection pauses, network timing, and GPU compositing — which is where the real bottlenecks are on web.
The problem with manual analysis
A Chrome DevTools performance trace recorded over a typical user session (navigating conversations, scrolling, viewing members) produces a JSON file exceeding 350,000 lines. The flame chart is virtually unreadable by eye for identifying patterns across hundreds of animation frames and long tasks.
Automated profiling with Chrome DevTools MCP
We use the Chrome DevTools MCP server connected to an AI coding assistant (OpenCode + Claude Code) to automate the entire profiling workflow:
Install the MCP server — add to your OpenCode MCP configuration (~/.config/opencode/opencode.json):
{ "$schema": "https://opencode.ai/config.json", "mcp": { "chrome-devtools": { "type": "local", "command": ["npx", "-y", "chrome-devtools-mcp@latest"] } } }Switch to the original branch you want to compare with your changes
Ask Claude Opus 4.6 to perform the profiling — example prompt:
Run the app on Chrome, in profile mode, connect via the Chrome DevTools MCP, set CPU throttling to 4x (recommended threshold to simulate a low-end device), start a performance trace, navigate through the app (open DM conversations, group rooms, scroll through messages, view member lists), stop the trace, and analyze the results. Compare before/after if applicable (Sync XHR (main thread), Animation frame avg, Jank, Long tasks, JS Heap).
Every now and then, manually scroll through the app using your mouse to make sure that the programmatic scrolling isn't skewing the data.
- **Switch to the branch where you