shakebugs.com

What is Shake used for?

Shake is a bug and crash reporting tool for mobile apps and websites. It attaches technical context to each report automatically so developers, testers, and product managers can reproduce and fix issues faster, instead of chasing vague descriptions over chat or email.

What it does in practice

• Mobile apps: You add the Shake SDK so testers and users can trigger a report from inside the app. Each ticket arrives with device, OS, app version, stack trace, logs, and reproduction steps already attached.
• Websites: A free Chrome extension lets anyone file a bug report on any site without coding, capturing the page context along with it.
• Triage and collaboration: Reports land in one place where teams can track issues, share notes, and assign crashes to teammates. Rules can auto-create and route tickets, for example flagging a billing-screen bug as high priority.
• Integrations: Reports can be forwarded to the tools a team already uses.

Who it suits

A useful next step is to pick one recurring annoyance — say, users reporting that login fails — and try filing a single report through the Chrome extension or a test build. If the attached context answers the questions your team normally asks by hand, the tool is earning its place.

How do I install the Shake Chrome extension to report bugs on any website?

Install the Shake Chrome extension from the Chrome Web Store: open the store listing, click Add to Chrome, confirm the permissions prompt, then pin the extension to your toolbar. On any website, click the Shake icon, describe the problem, and submit. Shake's page states the extension requires no coding and lets you send reports for any website; it also says no credit card is required to try Shake.

What happens after you submit

• The report is captured with page context attached automatically, so you don't have to screenshot or note your browser version by hand.
• Reports land in the Shake dashboard, where teams triage them alongside app reports.
• The page mentions 50+ data points per ticket, with 71 unique points cited for in-app reports; treat the exact count as product-stated rather than guaranteed for the extension.

When the extension is the right tool

Use it when a bug appears on a website you don't control or can't instrument with code—client sites, competitor flows, staging URLs, or third-party checkout pages. If the issue is inside your own mobile app, the SDK route is more appropriate, since it captures crashes and stack traces directly.

Practical setup tip

Create a project in Shake first, then connect the extension to that project so reports route to the right board. If you're evaluating it for a team, check Shake pricing for seat limits and features before rolling it out, and compare with a general-purpose reporter like BugHerd if you mainly need visual feedback on web pages.

What data points does Shake automatically attach to each bug report?

Shake's own page describes the automatic context it attaches to a report as "over 50+ data points" (elsewhere "71 unique data points"). The categories it names include:

• User activity history — a timeline of what the user did before submitting, so you're not relying on their written description.
• Device and environment details — device model, app version, and OS version.
• Crash diagnostics — stack trace, blackbox recording, and logs.
• Reproduction steps — captured alongside the report rather than typed up afterwards.
• Ticket history — whether the reporter is filing their 1st or 9th ticket.
• Server responses — e.g. a 403 response, cited as an example of what you can check when a user can't log in.

What this is good for: a tester or support agent files a report, and the developer opens a ticket that already shows the build, the device, the failing request and the path the user took. That replaces the usual back-and-forth ("which version? what did you click? send me a screenshot").

What to check before relying on it: the exact list of 71 points isn't enumerated on the page, and some items (custom user info, extra logs) are described as things you configure in the SDK rather than defaults. Confirm the specific fields you need for your stack — for example, whether your backend request/response bodies are captured — during a trial rather than assuming.

Practical next step: install the free Chrome extension on a staging site and file one test report, then compare the resulting ticket against what your team normally has to ask for manually. That single comparison tells you whether the automatic data covers your actual debugging gaps. For a broader look at the product, see Shake.

How does Shake help teams triage and assign bugs without paying per seat?

Shake's pitch is that bug reports arrive with context already attached, so triage becomes a matter of reading a ticket rather than chasing one down. The site advertises 50+ (in one place, 71) data points captured automatically per report — device, app version, OS, activity history, stack traces, logs and repro steps. For a triager, that means most "can't reproduce" round-trips never happen: you can see whether the reporter is on an old build, whether the failure was a 403 server response, or what the user did in the moments before a crash.

How assignment works in practice

The page describes inviting the whole team to collaborate — tracking issues, sharing notes and assigning crashes to teammates — and states that seats cost $0. It also mentions Rules: for a bug filed on, say, a billing screen, you can auto-create a ticket at high priority and route it to a developer, or filter it out entirely. Combined, that's the core of the no-per-seat model: unlimited people can read and act on reports, and routing is handled by rules rather than by a coordinator manually distributing work.

A realistic scenario

A QA tester hits a login failure on a Friday build. The report lands with OS version, build number and the server response attached. A rule tags it high priority and assigns it to the on-call mobile dev, who opens the stack trace and blackbox data without asking the tester a single question. A PM can meanwhile scan the same queue to see whether a given user is filing their first ticket or their ninth — useful for judging whether a "feature request" is a pattern or a one-off.

Where the trade-off sits

The value depends on the SDK being embedded in your app, and Shake states it adds 2.5MB to app size and doesn't affect speed. For websites, there's a free Chrome extension that requires no coding — but that's a reporter-side tool for testers and staff, not a substitute for instrumenting a production web app. The $0-per-seat claim is about collaboration seats; it isn't a claim that the product as a whole is free, and the site links to a pricing page you should read before assuming anything about plan limits.

Next step

Before committing, list the five questions your team asks most often when a bug comes in (which build? which OS? what did the user do first?). Then check whether Shake's automatic data points and Rules cover those, and confirm seat and volume limits on the pricing page.

Which integrations does Shake support to auto-forward reports to other tools?

Shake says it supports 1-click integrations that auto-forward reports into the tools a team already uses. The product page does not list the individual integration names, so treat "which specific tools" as something to confirm on Shake's own integrations page rather than assume.

Shake

A practical way to decide: if your team already triages work in an issue tracker, the integration matters mainly for whether a report lands as a new ticket with its attached data intact. If your team lives in chat, auto-forwarding is more about speed of awareness than structured tracking. Check the integrations page against your current stack before committing, and confirm what data actually transfers—device, OS, app version, logs and repro steps are the kind of fields worth verifying.

How does Shake handle GDPR and CCPA compliance for user data?

Shake states that it is GDPR and CCPA compliant, and that its SDK lets you control what user data is captured. The page emphasizes privacy controls as part of SDK customization: you can capture user info, attach logs, and protect data. That means compliance is handled mainly through configuration choices on your side, not through an automatic legal guarantee.

For a practical setup, treat Shake as one processor in your data map:

• Decide what personal data the SDK may collect (user IDs, emails, device identifiers, logs, screenshots).
• Mask or exclude sensitive fields before reports leave the device.
• Set retention and deletion rules that match your privacy policy.
• Document Shake in your GDPR Article 30 records and your CCPA service-provider terms.
• Check whether data is processed in a region that satisfies your transfer mechanism.

A concrete example: a fintech app can attach a stack trace and OS version but redact account numbers and auth tokens, then route billing-screen reports to a restricted team. That keeps debugging useful while limiting regulated data exposure.

Next step: review Shake's own privacy documentation and data processing terms, then compare them with your obligations. If you need a formal DPA or subprocessor list, request it from Shake before shipping.