diff --git a/README.md b/README.md index cf860763..f9794c93 100644 --- a/README.md +++ b/README.md @@ -9,11 +9,40 @@ Telegram-like interface. [Website](https://telesrv.net) · [OwpenGram client](https://owpengram.org/) · [Discussion group](https://t.me/telesrv_chat) · [Channel](https://t.me/telesrv) · [中文 README](README.zh-CN.md) +## telesrv-flutter: our own client + +**From our server to our own client.** + +We are reimplementing the client with Flutter. Chat lists, conversations, +messages, media, and group information are already part of a running product. + +![The running telesrv-flutter Windows client with folders, chats, messages, and group information](docs/assets/telesrv-flutter-windows.webp) + +Actual Windows application. **telesrv-flutter downloads are not yet available.** + +- **Our own chat organization:** folders, archived chats, unread markers, and + conversation search. +- **Our own messaging experience:** message bubbles, quoted replies, pinned + messages, and media. +- **Our own desktop workspace:** chats, messages, and group information side by + side, with layouts, themes, and window interactions we can continue to develop. + +Flutter powers the product interface. Our maintained TDLib fork handles +protocol and local state, with telesrv providing the server. We can build the +client and evolve it alongside the server to tailor an IM product to your needs. + +[Client showcase](https://telesrv.net/#flutter) · [Discuss client and IM customization](https://t.me/telesrv_net) + +
+Telegram Desktop and Android compatibility screenshots +

gramsrv running with Telegram Desktop gramsrv running on Android

+
+ ## Quick start with Docker Both [`main`](../../tree/main) and [`v2`](../../tree/v2) now provide the same diff --git a/README.zh-CN.md b/README.zh-CN.md index 37f55d67..438233ce 100644 --- a/README.zh-CN.md +++ b/README.zh-CN.md @@ -8,11 +8,36 @@ [English README](README.md) · [官网](https://telesrv.net) · [OwpenGram 客户端](https://owpengram.org/) · [讨论群](https://t.me/telesrv_chat) · [频道](https://t.me/telesrv) +## telesrv-flutter:我们自己的客户端 + +**从服务端,到我们自己的客户端。** + +我们正在用 Flutter 重新实现客户端。会话列表、聊天界面、消息与媒体、群资料面板, +已经落到实际运行的产品中。 + +![telesrv-flutter Windows 实际运行界面:文件夹导航、会话列表、聊天区域和群资料面板](docs/assets/telesrv-flutter-windows.webp) + +Windows 实际运行界面。**telesrv-flutter 暂未开放下载。** + +- **自己的会话组织:**文件夹导航、归档、未读标记与会话搜索。 +- **自己的聊天体验:**消息气泡、引用回复、置顶消息与媒体展示。 +- **自己的桌面工作区:**会话、消息与群资料并排呈现,大屏布局、主题与窗口体验可以持续演进。 + +Flutter 构建产品界面与交互,自有 TDLib fork 承接协议与本地状态,telesrv 提供服务端能力。 +我们有能力从头构建客户端,也有能力与服务端一起演进,围绕业务场景定制整套 IM 产品。 + +[查看客户端介绍](https://telesrv.net/#flutter) · [咨询客户端与 IM 定制](https://t.me/telesrv_net) + +
+Telegram Desktop 与 Android 兼容客户端截图 +

Telegram Desktop 正在连接 gramsrv Android 客户端正在连接 gramsrv

+
+ ## Docker 一键体验 [`main`](../../tree/main) 和 [`v2`](../../tree/v2) 现在都提供同一个一行启动入口: diff --git a/docs/assets/telesrv-flutter-windows.webp b/docs/assets/telesrv-flutter-windows.webp new file mode 100644 index 00000000..409a1187 Binary files /dev/null and b/docs/assets/telesrv-flutter-windows.webp differ