squawk 0.1.4

• The README opens with a recording of the flow: shake, circle the bug,
  Next, type a line, Send. Nothing in the package changes.
• The example gains lib/demo_main.dart, the order screen from that
  recording, with a deliberately wrong total to point at.

squawk 0.1.3

• The report sheet is two steps. First the screenshot fills the screen at
  its real size, with only a slim bar of tools at each end, so a finger
  has the whole screen to aim at. Then Next slides the form up over the
  drawing for the description and the email. Before, the form sat under
  the screenshot and took what height it needed, which left the picture
  at about half size and shrank it to a thumbnail when the keyboard came
  up.
• Two fingers pinch to zoom in, up to four times, and drag to pan. A Fit
  button brings the whole picture back. A second finger landing mid-stroke
  cancels that stroke instead of leaving a dot.
• The keyboard pushes the sheet and never the drawing. The sheet follows
  a drag from its grab bar and goes past a third of the way down or on a
  flick. Tapping the drawing or the Android back button returns to the
  drawing too, with the typed text kept.
• The example's dev harness has a System / Light / Dark switch, so the
  sheet can be checked against every theme mode.
• Nothing changes in what is sent: drawings were always stored in
  screenshot pixels and still are.

squawk 0.1.2

SquawkOptions.enabled, default true. Set it to false and Squawk renders your app and nothing else: no shake listener, no floating button, no log capture, and nothing left in the spool by an earlier build is uploaded. Squawk.show() returns silently rather than reporting the "nothing mounted" error, since a disabled build is a choice and not a mistake. It is a plain runtime value, so it can come from a --dart-define or from something only known once the app is running, such as whether the install came from TestFlight.

The README is rewritten so a reader can ship Squawk correctly without asking anyone. A new section, "Only on test builds", covers keeping Squawk out of the build the public gets, including the TestFlight-promoted-to-App-Store case and why Android needs a separate production build. The quick start and the example read the key from a --dart-define rather than hardcoding it. The limits are stated, retention matches the privacy policy, Slack delivery is described as it works now, and the theming section covers themes built by a widget above them, such as one sized with flutter_screenutil.

On pub.dev: https://pub.dev/packages/squawk

squawk 0.1.1

No behaviour change. Restructured how the capture session's future is returned so pub.dev's stricter analyzer no longer flags it, restoring the static-analysis score. On pub.dev: https://pub.dev/packages/squawk

squawk 0.1.0

The first working release, replacing the 0.0.1 name reservation. On pub.dev: https://pub.dev/packages/squawk

• Squawk widget: wrap your app, pass a project key, done. No native project edits.
• Shake opens the report sheet. Squawk.show() and an opt-in floating button open the same sheet; shakeSensitivity tunes the trigger on Android (iOS uses the system gesture).
• Annotate the screenshot with pen, arrows and text labels.
• Every report carries device and app info, the build mode, recent logs (captureLogs opts out), an optional reporter email, and any user context set with Squawk.setUser / Squawk.setMetadata.
• Offline spool: reports queue on disk and send when the network returns.
• SquawkOptions.theme / darkTheme match the report UI to the host app.
• Android and iOS only. Platform views (Maps, WebView) render blank in screenshots.