easylivechat_ui 0.1.65

Prebuilt, themeable Flutter chat UI for EasyLiveChat live customer support: launcher bubble, chat screen, pre-chat form, attachments and CSAT, driven by your widget config.

Changelog

0.1.65

• An EMPTY composer keeps facing the way the visitor writes. 0.1.64 turned the box around from the text in it, which left the moment before the first character — and every moment after a send cleared it — back on the workspace's direction. The keyboard's language would settle it and no Flutter API exposes it (reading UITextInputMode / InputMethodManager needs native code, which would make this a plugin), so the box now remembers what was last written in it, persisted per device, and falls back to the phone's own language before the workspace's. Type one Kurdish message and it stays right-to-left — next message, next visit.

0.1.64

• The composer faces the way you are typing. It took the workspace's direction, so a visitor writing Arabic, Sorani or Urdu into a left-to-right workspace typed into a box pointing the wrong way: caret on the wrong end, text against the wrong edge, punctuation on the wrong side. Neither iOS nor Android tells an app what language the keyboard is in, so the first strongly directional character decides — the rule dir="auto" uses on the web. An empty box, or one holding only digits or emoji, keeps the workspace's direction.
• Message bubbles do the same with their own text, so a thread where the visitor writes Arabic and the agent answers in English reads correctly on both sides instead of forcing one direction on the whole conversation.

0.1.63

• Requires easylivechat 0.1.50, which asks the server for the host inbox's configuration rather than the workspace default. Nothing in this package changed; the constraint is what stops a host resolving fresh from getting a core that still ignores its channel.

0.1.62

• Requires easylivechat 0.1.49, which sends an identified visitor's phone number on the resume path and persists it. Nothing in this package changed; raising the constraint is what stops a host resolving fresh from getting the old core and wondering why the agent still sees no phone.

0.1.61

• Images in the thread open full-screen. Attachments only ever rendered as 240×220 cover tiles, which is a thumbnail — a screenshot of the error the visitor is writing in about was unreadable, and no gesture enlarged it. Tapping one now opens a viewer with pinch-zoom, pan and double-tap-to-zoom (toward the point tapped, not the middle). A tap on the backdrop leaves, but not while zoomed in — there a tap is how a pan ends — and the × closes at any scale.
• The composer shows the picture you picked, not its filename. A pending image attachment was a paperclip chip reading IMG_20260814_113255.jpg, which says nothing about which of four screenshots was attached — the one thing worth checking before hitting send. It is now a 56px thumbnail, drawn from the bytes already read for the upload (so it appears instantly and costs no second download), tappable to preview full-size, with the remove × on its corner. Non-images keep the chip: a filename IS what identifies a PDF.
• New chrome strings close and removeAttachment in all 12 locales.

0.1.60

• The post-chat form's Submit button takes the host app's typeface. Its label carried a bare TextStyle, and ElevatedButton.styleFrom(textStyle:) replaces a button's text style rather than merging into it — so the family the app had set was dropped and Submit could render in a different face from the form around it. The style is now derived from the ambient textTheme.labelLarge, keeping the family (and the package it ships in) and overriding only size and weight, the way the end-chat dialog already did.

0.1.59

• The keyboard stays up when you send. Flutter's default finalize-editing unfocuses the field for TextInputAction.send, so tapping the keyboard's send key collapsed the keyboard on every message — and made the thread shake: the viewport grew as the keyboard left while the auto-scroll was already animating to the old extent, so the list scrolled, resized and settled again. Supplying onEditingComplete replaces that default, which is the documented way to keep focus; the send stays on onSubmitted so nothing sends twice, and clearComposing() still runs so an in-progress IME composition does not survive the send.

0.1.58

• Requires easylivechat 0.1.48 for EasyLiveChat.reset(). Nothing in this package changed; raising the constraint is what guarantees a host resolving fresh gets the new API rather than a version without it.

0.1.57

• A message that is only pictures no longer sits in a bubble. The bubble exists to put a surface behind text, and wrapped around a photo it read as a thick coloured frame — on the visitor's own side that is the full accent colour, so their own images arrived matted in it. The tile already rounds its own corners, so the photo now renders bare, the way every other messenger draws one. Deliberately narrow: a caption still gets its bubble, and so do file chips and unavailable-media placeholders, which read as controls and would float loose without a surface behind them.

0.1.56

• The thread follows the visitor's own message down again. Auto-scroll was gated on already being near the bottom, on the assumption that a send always comes from there — it doesn't. Scroll up to re-read something, answer it from where you are, and the message landed off screen, so the thread looked like it had swallowed what you just sent. The keyboard opening moves the scroll extent too, which could push a visitor out of the window without their having scrolled at all. Their own message now always scrolls into view. An incoming one still respects the gate, so an agent's reply cannot yank someone out of history they are in the middle of reading.

0.1.55

• Requires easylivechat 0.1.47, which stops the replying agent's name and photo being wiped off a bubble by the delivery receipt the visitor's own client sends moments later. Nothing in this package changed: MessageBubble renders whatever identity the message carries, and it was the message losing it. Raising the constraint is what guarantees a host resolving fresh picks up the fix rather than staying on 0.1.46.

0.1.54

• The thread shows sent/read ticks on the visitor's own messages: a clock while the send is in flight, one tick once the server has it, two in the workspace accent once an agent has read it. Matches the web widget, so a customer who uses both surfaces reads the same marks. A failed send keeps its worded retry link — it is the only state the visitor can act on, so it stays a sentence rather than becoming an icon to interpret. Each state carries a screen-reader label (messageSent, messageRead, and the existing sending), translated into all 13 locales — the tick is the entire visual, so without them it announced nothing at all. MessageBubble takes an optional agentLastReadAt for hosts embedding it directly; omitted, it simply never shows the read state.

0.1.53

• Session-divider dates and times are formatted in this package instead of through the host's MaterialLocalizations. Two of the 13 chrome languages — ckb and kmr — have no Flutter Material localizations, so a host supporting them must supply its own delegate, and one with a bad pattern rendered a date as literal format characters (٠٨/٢٢٤/YY) with no way for the SDK to tell that from a real date. Now built from the parts: dd/MM/yyyy and HH:mm, Western digits, wrapped in a Unicode isolate so a numeric run keeps its own reading order inside right-to-left copy.
• The post-chat form's Submit button is full width, matching the fields above it, instead of shrinking to its label in the middle of the sheet.

0.1.52

• The date on a session divider reads correctly in right-to-left locales. 12/08/2026 is digits joined by neutral characters, and neutrals take the direction of the text around them — so in Kurdish (kmr, ckb) the groups were laid out right-to-left and a correct date arrived on screen looking like ٢٢/٠٨/٢٢٤. Arabic hid the bug only because its short format uses a month name, whose strong letters pin the order. The date and the "you left the chat" time are now wrapped in a Unicode isolate, so each keeps its own reading order without leaking direction into the sentence around it.

0.1.51

• Kurmanji (kmr): corrected the wording of the failed-send retry line.

0.1.50

• Requires easylivechat ^0.1.45. The floor moves because behaviour this package presents now depends on it: "Close chat" only offers the post-chat survey on a second visit with core 0.1.45. ^0.1.42 still allowed 0.1.45, but it also allowed 0.1.42 — and a consumer holding an old lockfile would keep a UI whose end-chat button silently does nothing, which is the bug that release fixed.
• Corrected the Kurmanji (kmr) strings. Seven were still untranslated Latin-script placeholders — the close-chat button, the survey skip, the session notices and the post-chat title all showed romanised text to a Badini reader — and the rest are retranslations from a native speaker.

0.1.49

• Activated the lints. flutter_lints was a dev-dependency with no analysis_options.yaml including it, so local analysis had no rules at all while pub.dev scored against lints_core — which is how a missing pair of braces cost 10 points with every local check passing.
• Fixed the guard clause it flagged in the closed-notice view, and three const opportunities in the example. No behaviour change.

0.1.48

• The auto-greeting shows a face and a name again. An inbound bubble now always gets an avatar when the workspace has the switch on, instead of only when the message already carries a name or a photo. A chat opened before it is assigned has a greeting attributed to nobody, so the very first bubble of the thread was blank while every later one had a photo — and it stayed blank for the life of the conversation. The web widget has always drawn a circle here and fallen back to an initial; this matches it. System notices are unaffected: they render as centred lines and never reach the avatar path.
• Needs the matching server change to put a name on a greeting that was written while nobody was assigned — the client half only guarantees the circle.

0.1.47

• Web is no longer a supported platform. The package declares android, ios, linux, macos and windows. It is not that the UI cannot run on web — it does under the JS compiler — but it is not a platform we test or support, and dart compile wasm genuinely fails: cached_network_image pulls flutter_cache_manager, which reaches for dart:io, and neither has a WASM-ready release. The web product is the embeddable script-tag widget. A Flutter app targeting web will now be told this dependency does not support that platform.
• Added example/, which pub.dev requires and which this package never had. It shows both integrations: the launcher in a Stack, and the screen pushed as a route with the end-chat button.
• README rewritten as a guide rather than a summary: install, a complete runnable main.dart, the iOS Info.plist keys that attachments require (without them the picker silently fails), a phase table, recipes for identify / unread badge / theming / ending a chat / locales / custom picker, and troubleshooting for the failures people actually hit.
• description shortened to fit pana's 180-character limit; added topics; formatted with dart format.

0.1.46

• Requires easylivechat ^0.1.42. The thread reads EasyLiveChat.hasOlderHistory, which does not exist in earlier cores — the same compile failure 0.1.45 was cut to fix, one getter later.
• The thread no longer pulls a page of history the moment it appears. That was right when a conversation was a single visit; now that a returning customer resumes a thread spanning months, it dragged the previous visit straight back on screen, underneath the greeting for the visit just started. Older messages arrive when the visitor scrolls up, or asks for them.
• "Load earlier messages" is a real control again. It rendered nothing when idle, on the reasoning that loading was automatic; with the eager load gone that would have stranded history on a session too short to scroll. The list is also always draggable, so the pull gesture works even when the thread fits the screen.

0.1.45

• Requires easylivechat ^0.1.40. 0.1.44 drew the submitted post-chat survey in the thread through ChatMessage.postChat, but still allowed core 0.1.39, where that getter does not exist — so every host outside this repository failed to compile with "The getter 'postChat' isn't defined for the type 'ChatMessage'". In-repo builds resolve the sibling core through pubspec_overrides.yaml, which is why the gap only showed up downstream.
• The post-chat survey a visitor filled in renders where they filled it in, instead of below newer messages. Shipped in 0.1.44 but never listed here.

0.1.44

• EasyLiveChatScreen can draw its own app bar: showAppBar: true gives a back button and an X. They are different actions on purpose — backing out leaves the conversation open so the visitor can return to it, while the X is the explicit end that confirms first and then shows the post-chat survey. Off by default, since most hosts push the screen into a route that already has an app bar and would otherwise get two. appBarTitle overrides the title, which defaults to the workspace's own.
• The end-chat confirmation now takes its typeface from the host app. styleFrom(textStyle:) REPLACES a button's text style, so the bare TextStyles it used dropped the app's fontFamily and fell back to Material's default — the two buttons could render in different faces from each other and from the rest of the app. Both are also the same weight now.

0.1.43

• An arriving agent reply now chimes, the way the web widget always has — the visitor is usually looking at something else in the host app, so a thread that updated silently was simply missed. Honours the workspace's soundEnabled / soundUrl widget config, falling back to a bundled default (the same audio file the web widget serves). Only AGENT messages ring, not the visitor's own sends, bot greetings, or transfer notices. Adds an audioplayers dependency.
• EasyLiveChatEndChatButton is a plain X instead of the speaker-notes-off glyph, which read as a mute control rather than "close this".
• The chat screen reports read receipts while it is on screen (on mount, on each arrival, and on app resume), so the agent's ticks turn green. Needs easylivechat 0.1.39.

0.1.42

• "Typing" now follows the FIELD, not the keystrokes: it keeps announcing for as long as the composer has text and stops the moment it empties (or on send). Previously it stopped after ~1.5s of no keystrokes, so pausing mid-sentence made the indicator disappear on the agent's screen while the visitor was still composing.

0.1.41

• The visitor's "typing" now keeps announcing itself while they type. It was sent once on the first keystroke, so an agent app — which clears its indicator ~4s after the last event — stopped showing it mid-sentence with no state change left to fire another event. Re-announced at most every 2s.

0.1.40

• End-chat confirmation redesigned: the workspace's own colors and text direction, 24px corners, a solid confirm button and a quiet cancel stacked full-width instead of two cramped text buttons in the host app's Material theme. EasyLiveChatEndChatButton and confirmAndEnd take an optional theme so a host that themes the chat screen can match the dialog to it.
• The send button now hides while the composer is locked, like the attach button already did — a live accent-colored send beside a disabled field promised something the composer would refuse.

0.1.39

• Typing indicator rebuilt: staggered messenger-style hop (each dot takes its turn to rise and brighten) instead of a flat synchronized fade — and the dot spacing no longer collapses under RTL, where the old physical padding stacked the dots on top of each other.
• Bubble tail corners are now logical (start/end), so the tail hugs the correct side in RTL layouts for both message bubbles and the typing row.

0.1.38

• Repository moved to a dedicated public home: m4hmoud/easylivechat-flutter-sdk. No code changes.

0.1.37

First pub.dev release. Previously consumed as a git dependency (flutter-sdk-v0.1.x tags in the repository); version numbers continue that series.

• Launcher bubble + full chat screen: pre-chat form, thread, composer, attachments (image/file), CSAT, offline form — all server-config driven.
• Backing out no longer ends the conversation; it resumes on reopen. New EasyLiveChatEndChatButton (and static confirmAndEnd) is the explicit, localized end-chat affordance; EasyLiveChatScreen.confirmExit is deprecated and inert.
• Transfer notices render as centered system lines, localized to the visitor's language via the server's structured i18n key.
• Post-chat survey is skippable; composer respects read-only/closed states with localized notices and working-hours copy.
• 13 chrome locales (en, ar, ckb, kmr, de, es, fr, hi, it, pt, tr, ur, zh) with per-key and per-locale host overrides; full RTL support.