Flutter rewrite of AndroidIRCx, focused on preserving behavior, features, and UX parity with the existing React Native application.
This repository is an active Flutter rewrite in release hardening.
Implemented in the current Flutter app:
- network list, server directory, add/edit flow, identity profiles, and in-chat network switching
- TCP/TLS IRC transport, IRCv3 WebSocket transport, reconnect/backoff, and foreground-service integration
- IRC parser, ISUPPORT, numerics, CAP 302, SASL PLAIN/SCRAM-SHA-256/EXTERNAL, CTCP, and IRCv3 message features
- server, channel, query, notice, and DCC tabs with command suggestions and rich channel user actions
- encrypted local message history with retention/search/export support
- DCC CHAT/SEND, safe file picking, transfer progress, media cards, previews, downloads, camera/gallery capture, and in-app audio/video playback
- onboarding, consent/privacy screens, app lock, notification/display/writing settings, themes, backup/restore, ignore lists, auto-away/highlights/sounds, auto-rejoin, diagnostics, and crash reporting
Still outside the default-client release scope:
- E2EE and scripting are later product/security decisions
- ads/IAP are now an explicit monetization slice: top banner ads, opt-in rewarded ads for temporary banner-free time, and one-time no-ads purchases
- WebRTC calling is not planned
- upload/share endpoints are deferred until a concrete product endpoint exists
- TLS/SSL -- full encrypted connection support
- SASL -- PLAIN, SCRAM-SHA-256, EXTERNAL (client certificates)
- Encrypted History -- local message bodies encrypted with AES-256-GCM
- Secure Storage -- platform-backed storage for server passwords, SASL secrets, channel keys, and certificates
- App Lock -- PIN and biometric with auto-lock on background/launch
- Crash Reports -- sanitized on-device reports with secret redaction
AndroidIRCX is open source and contributions are welcome.
Areas where you can help:
-
IRC protocol -- new IRCv3 capabilities, IRCd-specific features
-
Testing -- more edge cases, integration tests
-
Translations -- add or improve translations via Transifex
-
UI/UX -- accessibility, new themes, layout improvements
-
Documentation -- guides, tutorials, examples
-
Security -- audit, improvements, new encryption features
-
Before submitting a PR:
flutter analyze
flutter test # Must pass all| Standard | Coverage |
|---|---|
| RFC 1459 | Full compliance |
| RFC 2812 | Extended numeric support (390+ handlers) |
| IRCv3 | 27 capabilities requested, full implementation |
| SASL | PLAIN + SCRAM-SHA-256 (RFC 7677) + EXTERNAL |
| DCC | SEND, CHAT |
| CTCP | Full (VERSION, TIME, PING, ACTION, etc.) |
IRCap (c) Carlos Esteve Cremades, 1997-2026 - the legendary mIRC script that inspired AndroidIRCX's away system, protection features, writing styles, and the IRcap theme. If you used mIRC in the 2000s, you probably know IRCap. Its futuristic design and complete feature set set the bar for what an IRC experience should be.
IRcap theme for AndroidIRCX by ARGENTIN07, based on the original IRCap theme.
Translations: ARGENTIN07 and Cubanita83 (Spanish), Yusbastian Lemon (Indonesian). See the full credits in the app's Credits screen.
As an open-source creator, I deeply respect the work of Linus Torvalds and Richard Stallman for the free/open-source software movement. Their vision and persistence were a direct inspiration for building this app as open source.
GNU General Public License v3.0 or later (GPL-3.0-or-later)
Copyright (C) 2025-2026 Velimir Majstorov
This program is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version.
This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.
You should have received a copy of the GNU General Public License along with this program. If not, see https://www.gnu.org/licenses/.
This project was built with modern tools, including AI-assisted development.
Like robotics in manufacturing, autopilot systems in agriculture, and autocomplete in software, AI is a tool -- no more, no less.
AI did not build this project on its own. Every decision, architectural choice, security consideration, and final line of code was reviewed, validated, and maintained by a human engineer with more than 25 years of professional experience.
AI did not replace engineering judgment; it accelerated routine work so more time could be spent on architecture, quality, and usability.
If you prefer software created without automation or AI assistance, that choice is fully respected. At the same time, refusing tools has never stopped progress -- it has only determined who participates in shaping it.
This project exists to contribute something real to open source, with practical value and long-term maintenance. You are welcome to:
- use it or study it
- fork it or improve it
- or simply ignore it
All are valid choices.
Builders shape the future in silence. Spectators explain it when the work is already done.
In the end, technology moves forward with or without permission. The only question is who chose to be part of it.
Some build loudly. Others build correctly.
Those who recognize the work will understand. Time will explain the rest.
🜂🜃🜂
