What is expo-dynamic-tray?

expo-dynamic-tray is a component library for React Native and Expo apps that gives developers a bottom sheet tray, the kind of panel that slides up from the bottom of a screen. Instead of just sliding into place, the tray uses a single spring animation to move its position, fade its backdrop, and scale itself all together, so it feels like it grows into view rather than snapping open. The tray sizes itself automatically based on whatever content is placed inside it, so there is no need to set fixed heights. It also supports multiple views within one tray, with a real history stack: calling setView moves to a named view, and goBack unwinds through however many views were opened, similar to screens in a navigation stack. Switching between views includes a crossfade and scale effect so the transition feels continuous rather than abrupt. One practical feature is keyboard awareness. Using the react-native-keyboard-controller library, the tray lifts itself above the on screen keyboard and stays attached to it as the keyboard appears or moves. Users can also dismiss the tray by swiping or flicking it away, and the library measures both how far a user dragged and how fast, then snaps back with a spring if the swipe does not meet the threshold. The tray supports a persistent footer area that can hold buttons or other content. This footer slot stays mounted while switching between views, so buttons do not disappear or jump around during navigation. Developers can open and control the tray either declaratively, using a Trigger component, or imperatively, by calling functions from a useTray hook anywhere in their component tree. The project is written entirely in TypeScript, so all its components and functions are typed. Installation requires cloning the repository and adding a handful of peer dependencies for gestures, safe area handling, keyboard tracking, and Expo's UI package. The README includes code examples covering setup, a simple single view tray, imperative control, multi view navigation, and a shared footer, along with a full prop reference table for each exported component.