Skip to content

Framework7 Kitchen Sink Runtime Check

Focused runtime validation for the Framework7 8 kitchen sink mobile demo.

Home route renders

Open the generated kitchen sink home page and confirm that the curated landing shell renders inside the mobile design preview.

Home shell checks

The landing page should show the new hero, curated showcase cards, and the route entry points without breaking the Framework7 shell.

Hero renders
The kitchen hero section appears in the preview.
Routes exposed
The curated route links are present and selectable.
Shell intact
The page still loads as a routed Framework7 app shell.
Render the home page in Design View
Confirm the hero container exists
Confirm the curated route link exists

Standard showcase route works

Navigate from the home page into the standard Framework7 showcase and confirm the routed page and popup sample both render.

Standard showcase checks

The routed Framework7 page should load and its popup sample trigger should stay interactive from the sample area.

Route transition
The showcase route resolves to the standard hero page.
Popup trigger works
The popup sample trigger remains clickable inside the routed experience.
Native surfaces
Cards, chips, and popup entry points stay visible in the updated shell.
Open the standard showcase from the home page
Wait for the standard hero block
Click the sample popup trigger without breaking the page shell

App Connect showcase reacts

Navigate into the App Connect showcase, then toggle the page from launch mode to operations mode and confirm the bound state updates render.

App Connect checks

The App Connect page must load its bound layout and respond when the mode toggle switches the view from launch to operations.

State toggle
The segmented control flips the page into operations mode.
Bound progress
The progress surface remains present after the state change.
Mode copy updates
The view exposes the operations story text after the toggle.
Open the App Connect showcase route
Switch from Launch to Operations
Confirm the operations state text and progress surface remain visible

Capacitor showcase loads

Navigate into the Capacitor showcase and confirm that the page renders the device-aware components and the routed page shell stays intact.

Capacitor checks

The Capacitor showcase should render the routed hero plus the app, network, and geolocation component surfaces without breaking the page.

App component
The Capacitor App component is present on the page.
Network component
The Capacitor Network component is present on the page.
Geolocation component
The Capacitor Geolocation component is present on the page.
Open the Capacitor showcase route
Confirm the routed hero renders
Confirm all three Capacitor component nodes are present

Conclusion

The runtime probe is complete. Use the follow-up link to continue with the broader product tour set.

Next steps

Continue with a broader Wappler tour after the kitchen sink runtime check.

Runtime verified
The mobile demo probe completed.
Finish the validation pass
Return to a broader product tour if needed