[Music] in the platform analytics experience we have two ways to build your dashboard so whenever you are consuming a dashboard most likely it is built through the simple way the inline editor dashboard but it could also be it was built through the platform's UI Builder now why do we have those two approaches in most if not all use cases the easy to use inline editor is your dashboard builder of choice it's targeted at the everyday dashboard Builder that user that just wants to quickly create or edit a dashboard it has the drag and drop and resizing capability and a quick way to drop in new widgets for you to start configuring Target user Persona here is basically everyone unless you would have a very specific use case you might need some UI Builder type type of configuration for to re-emphasize the inline editor should be your dashboard builder of choice if you want a quick and easy way for dashboard configuration or expect others to maybe modify it you should default into this easy to use dashboard editor whether you are using the technical dashboard or the simple inline editor dashboards both are in the same dashboard dropdown so they can be easily found for your end users that experience is the same so they might not know whether they are looking at an inline edited dashboard or a technical one with the technical dashboard you would have technically all types of features and capabilities you would also have with the UI Builder application inside our platform you can use more types of components maybe set some very specific data binding or event handling you would like to add to your dashboard UI do know that you would need citizen developer type of skills required to be configuring that more technical approach only if you are an admin user you will see a similar screen when creating a new dashboard any other user will not get this popup and will be automatically navigated into the simple inline editor so upon choosing the inline editor this will bring you to the editor UI showing the user an empty screen where they can start adding content this can be components you add and configure from scratch or maybe existing content from your library the user can use the easy drag and drop to build their dashboard experience this is the same experience as people might be familiar with by using the responsive dashboards in the core UI it is a very feature-rich dashboard building and as said before really targeted for the everyday dashboard Builder simple to use Simple to configure and also userfriendly for anyone you might be sharing the dashboard with as mentioned admins will have another option to build a dashboard UI that is technically built through our platform's UI Builder application this does come with the effect that it's more targeted to developer type of Builders to create it and absolutely not suitable for the everyday dashboard Builder the benefit of using this one is that it will allow you as the Builder all the capabilities the UI Builder has for example around specific data needs or event handling or scripting once you created the placeholder you can immediately see that this technical dashboard is available the same way as your other dashboards the big benefit of that is that for your dashboard consumers will just see it as a regular dashboard this dashboard dropdown easily allows to navigate in between dashboards but the actual technique behind the dashboard might differ if we start editing the just created technical Dash board it will literally bring us to the UI Builder application from there you then have all the capabilities that the UI Builder has for their normal UI page creation purposes you see the UI Builder application with the UI page layout on the left and the configuration on the right from here you can use those more advanced capabilities within the data binding and Page scripting or set some specific event for UI component interaction it also allows you as the more advanced Builder to start building a dashboard UI layout using all components from the library including the data visualization and filter components once done you can save the page and it will appear as a UI Builder created page within your dashboard application remember only use this when you need those specific requirements that the normal inline editor dashboard wouldn't be able to do [Music]