Skip to main content


Shake's user interface explained and instructions on how to customize it.


The Shake UI consists of nine screens, and here's how they're related:

Shake screens structure

Opening Shake

You can decide to open either Shake's Home screeen or New ticket screen, depending on the flow you want to achieve. Listed below are some common use cases that show where you might like to add Shake to your app. Of course, it's up to you to decide what best suits your app UX.

Internal feedback collection

This entry point is often used during internal testing. Your testers or office colleagues are told to invoke Shake whenever they notice a bug or have a suggestion. In this case, instruct Shake to open the New ticket screen:

Open Shake New ticket screen

Production ticketing system

In production, apps usually add Shake under My account or Settings → Help. There, they have a Submit feedback button that opens Shake's Home screen:

Open Shake Home screen

Internal and production crash reporting

Lastly, Shake can open automatically after your app crashes. Enable Crash reports and enable the Ask for crash description sheet so your users can describe what happened before your app crashed on them:

Open Shake New ticket screen after the crash

Design and customizations

Shake supports dark and light mode out of the box, there is no need to code anything. Its UI will automatically adapt depending on your app design settings.

Shake also supports white labeling, you can change its colors and text from the code.

Lastly, Shake mobile UI has been localized to support numerous languages. Your users whose default device language is set to one of those will automatically use Shake in their native language.

⚡️ Shake is improved every week. Stumbled upon a bug? Want a new feature to be added? Create new tickets and upvote existing ones on the Public feedback board.