Within our Tulip instance, we maintain a Master Base Layout application that serves as our standard template, containing all of our required corporate headers, footers, and brand assets etc. When our developers build a new application, they must manually locate this master app, duplicate it, move it into their designated folder, and rename it before they can begin building.
I’d like to propose introducing a “Workspace Default App Template” setting for platform administrations, which would allow admins to designate a specific App ID as the global default starting point for their environment. When a user clicks the standard “Create App” button, rather than generating a blank canvas the platform would automatically perform a backend duplication of the designated master app and place it into the user’s current folder. This would seamlessly replace the blank app default with our customised corporate starting point.
If our (currently UI-only) template evolves to include standard app variables or placeholders, this approach guarantees that all logic remains perfectly intact. This enhancement would lower the barrier to entry for new builders, help enforce enterprise governance without administrative overhead, and accelerate the overall time-to-value for new application development.