daybook_feedback 0.3.4

In-app feedback for Flutter: shake, screenshot, a button or a two-finger long press opens a report of the moment, a process step by step, or a recording, marked up and noted. Only for people approved [...]

0.3.4

• Builds for Android with Android Gradle Plugin 8 as well as 9. With AGP 8, 0.3.3 failed in its own build script ("Unresolved reference: compilerOptions"); now the Kotlin plugin is applied when AGP does not compile Kotlin itself, and the JVM target is set on the compile tasks. Nothing else changed.

0.3.3

• Reports no longer fail with 403 "only people approved in Daybook can file" half an hour after the app starts. The SDK renews its session before it runs out, and once more if a report is refused.
• A screen capture that fails the instant feedback opens is tried again after the next frame. When it still fails, the message says where it failed.
• The server's message for an expired session now says the session expired, rather than that the person isn't approved.

0.3.2

• When the screen can't be captured, the SDK says so instead of doing nothing: the capture bar shows "Couldn't capture", and the composer gives the reason. The report can still be sent without a picture.
• DaybookFeedback.lastError holds the reason, for your own diagnostics or error reporting. It is not raised as an error, so a guard that turns the SDK off on its errors is not tripped.
• Capture waits for a pending frame in release builds too, not only in debug.
• When the engine can't encode a captured frame as PNG, the SDK encodes it itself from the frame's pixels, the way screen recording already reads them. On a TestFlight build Capture gave no picture while recording worked on the same phone.
• Every report carries a short log of what the SDK itself tried: each capture, its size and colour space, which encoder it used, and the error when there was one. So when capture fails on somebody's phone, their next report, even a video or a few words, says why. It holds the SDK's own events only, never app data.

0.3.1

• The floating button can start clear of your app's bottom tab bar, or in another corner: DaybookFeedback.init(buttonPlacement: FeedbackButtonPlacement(...)).
• Where somebody drags the button is remembered on the device. It no longer jumps back after every report or app start.

0.3.0

• Feedback starts with a choice: This moment, Step by step, or Record a video. A system screenshot goes straight to This moment.
• Step by step, for processes and QA: capture the app a step at a time from a small bar, then give each step a note and its own markup. Up to 10 steps, shown in order in triage.
• The capture and recording bars are compact and can be dragged out of the way of your app's own bars.
• The keyboard no longer covers Send, and tapping outside a field or scrolling closes it.

0.2.0

• Drawn in your app's own theme, light and dark, and switches when your app does: put it in your MaterialApp with builder: DaybookFeedback.builder. wrap() still works, and takes theme and darkTheme.
• Mark up the screenshot full-screen: numbered pins, freehand and boxes, undo and clear. What is drawn is in the picture that is sent.
• Point at it: tap the real thing in the app to pin it, with a ring round it.
• Record: start, use the app, stop. Up to a minute as an MP4 of the app with taps shown, with no permission to grant.
• What's new and What to test for the version running, written on the project's Daybook release.
• Send is always on screen.

0.1.2

• Works alongside newer plugins: sensors_plus 7, device_info_plus 12 and 13, and package_info_plus 9 and 10 are now accepted, so an app already on them can add the SDK. Nothing else changes.

0.1.1

• Package details only: the repository link and the example app's signing team are removed, and the iOS pod describes itself. Nothing changes in your app.

0.1.0

• The first Flutter SDK. It files feedback like the web widget: a screenshot of the app's own screen, numbered pins that name what they point at, the message, the kind, the reporter's email, and the screens that led there.
• Only for people you approve. The app must call identify(), and a new person waits in Reporters until someone approves them; until then the SDK shows nothing and listens to nothing.
• Opened by shake, a system screenshot (iOS, and Android 14+), a floating button or a two-finger long press, as the key allows — or from your own code with DaybookFeedback.open().
• Reports queue while offline and go when there is a connection.