Comparison with other React Native toast libraries
How Super Toast compares to sonner-native, react-native-toast-message, and native system toasts.
Every React Native toast library makes one decision that shapes everything else: where the toast is rendered. Most render it as a React view inside your app's view tree. Super Toast renders it natively, in a layer above that tree.
That single difference is why a toast can be covered by a modal, and why Super Toast's cannot.
The same flow in three libraries
Each recording runs the same Android screens: open a page sheet modal and show a toast, then open a transparent modal and show another.
In both, the toast is covered by the page sheet and dimmed underneath the transparent modal's backdrop, because it is part of the view tree the modal is covering.
Super Toast draws the same toast in a separate native window, so it stays fully visible and tappable while the modal is open.
Where each library renders
| Rendering layer | Extra dependencies | Toast content | |
|---|---|---|---|
| sonner-native | React views in your view tree | An animation and gesture stack | Any JSX |
| react-native-toast-message | React views in your view tree | None required | Any JSX, via custom toast components |
Native system toasts (for example ToastAndroid) | The OS toast layer | None | Fixed, minimal, platform-specific |
| Super Toast | A native window above the view tree | None | Serializable data rendered natively |
Check each library's own documentation for the current details: this table describes the approach each one takes, not a snapshot of every feature.
What you give up
Rendering natively is a trade, not a free win:
- No arbitrary JSX. There is no
toast.custom. Content is a title, description, icons, and buttons; see Styling for what you can set. - The New Architecture is required, because the native module is a TurboModule.
- A native rebuild is required. Expo users need a development build, not Expo Go.
If you need a toast that embeds your own components, and your toasts never have to sit above a native modal, a view-tree library is the simpler choice.
When Super Toast is the right pick
- Toasts have to be visible over native modals, form sheets, bottom sheets, or dialog windows.
- You want the toast to stay tappable while a modal is open, so actions like Undo still work.
- You would rather not add an animation and gesture stack just to show a toast.
- You want iOS and Android toasts that look and behave the same.
Start with Installation, or read Architecture for how the native layer works.