The front-end view works the same as the editor view. The front-end view is used to optionally render a different output for your block when it is displayed on the front-end of your website (as opposed to how it’s rendered when viewed in the WordPress editor).
If you want your block to appear the same way on the front-end as it does in the editor, you can usually skip the front-end view to save time. If nothing is added to the front-end view, Wicked Block Builder will automatically generate it based on the editor view.
One important thing to note is that the front-end view of your block is not generated when a page is viewed on your website. Instead, the content for the front-end is generated when you edit a page in the editor and click save. When you click save, WordPress asks every block on the page to provide its HTML for the front-end view. This HTML content is then saved to the database. When WordPress displays a page, it simply renders the HTML that was saved to the database for the page. It does not generate the HTML for each block on the fly.
The exception to this is dynamic blocks. Dynamic blocks are generated on the fly when a page is displayed.
Note that only components that generate content can be added to the front-end view. Components like TextControl are used to input content into your block. They don’t generate content so they are not displayed in the front-end view.
Note: the block.isSelected condition is always false in the front-end view. Meaning if you add a condition to an element or component that only outputs the item if block.isSelected equals true, the item will not be output on the front-end.