import type { ComponentType } from "react";
import type { StyleProp, ViewStyle } from "react-native";
import type { MaterialCapabilities } from "./material-resolution.js";
export interface FrostProps {
    intensity: number;
    tint: "light" | "dark";
    style: StyleProp<ViewStyle>;
    experimentalBlurMethod?: "dimezisBlurView";
}
export declare let FrostView: ComponentType<FrostProps> | undefined;
export declare let requiresBlurTarget: boolean;
/** Whether the browser renders a CSS backdrop filter, the one thing the web frost needs. */
export declare function backdropFrostSupported(): boolean;
export declare function materialCapabilities(): MaterialCapabilities;
/**
 * The capabilities a surface renders with, safe to read during render on every
 * platform. On the web the probes above (`CSS.supports`, the user agent) are facts
 * only the browser knows, so a server render cannot see them and a hydration render
 * must not act on them: React would find markup the server never shipped and rebuild
 * the tree. Both of those renders get the server assumption instead, and the real
 * probes land in the commit right after, the same contract `useHydrated` gives the
 * viewport axis. A plain client render (no server markup) reads the probes at once.
 */
export declare function useMaterialCapabilities(): MaterialCapabilities;
//# sourceMappingURL=material-runtime.d.ts.map