Note: WebF development is nearly identical to web development - you use the same tools (Vite, npm, Vitest), same frameworks (React, Vue, Svelte), and same deployment services (Vercel, Netlify). This skill covers one of the 3 key differences: routing with native screen transitions instead of SPA routing. The other two differences are async rendering and API compatibility.
WebF does NOT use traditional Single-Page Application (SPA) routing. Instead, it uses hybrid routing where each route renders on a separate, native Flutter screen with platform-native transitions.
In Browsers (SPA Routing) Traditional web routing uses the History API or hash-based routing:
Configura il routing ibrido con transizioni dello schermo native in WebF: configura la navigazione utilizzando il routing WebF anziché il routing SPA. Da utilizzare quando si configura la navigazione, si implementano app multischermo o quando react-router-dom/vue-router non funziona come previsto. Fonte: openwebf/webf.