Struct App 

pub struct App<State, Logic> { /* private fields */ }

A Frust application: the app state plus the app_logic function that maps it to a view tree.

Construct with App::new and start the event loop with App::run, optionally naming a desktop identity with App::desktop in between.

The view type is intentionally not a parameter of this struct: capturing a free fn app_logic(&mut State) -> impl View<State>’s opaque return type into a stored type parameter defeats method resolution (the opaque type’s trait bounds can’t be re-proven on the already-typed value). Instead App::run infers the view type freshly at the call site, so App::new(state, app_logic).run() compiles for both impl View and concrete-typed app_logic.

Implementations

impl<State, Logic> App<State, Logic>

pub fn new(state: State, logic: Logic) -> Self

Create an app from an initial state and its app_logic.

logic is a FnMut(&mut State) -> impl View<State> re-run each frame to produce the current view tree.

impl<State: 'static, Logic> App<State, Logic>

pub fn desktop(self, config: DesktopConfig) -> Self

Give the app a desktop identity — name, reverse-DNS id, window icon, native menu bar, last-window-close policy (see DesktopConfig).

Optional: an app that never calls this runs with DesktopConfig::default(), which is the dev-preview window exactly as it has always been. Each per-OS shell reads the fields it can act on and ignores the rest (Linux has no native menu bar, macOS wants an application icon rather than a window one, and so on).

frust::App::new(AppState, app_logic)
    .desktop(frust::DesktopConfig::new().with_app_name("Huddle"))
    .run()
    .unwrap();

pub fn run<V>(self) -> Result<()>

where V: View<State>, Logic: FnMut(&mut State) -> V + 'static,

Run the app in the desktop window until it is closed.

Blocks the calling thread on the platform event loop. Returns once the window closes, or an error if the window/GPU surface could not be created. The concrete view type V is inferred from logic.

Desktop-only: on Android the app is driven by the JNI bridge that android_app! generates and on iOS by the C-ABI entry points ios_app! generates, not by this loop.